How should a fresher in testing handle the final stage of testing?
I have 4 years of previous experience in support roles. Now, I started working for a new company. Initially, I was told that there is some specific requirement that they are trying to map me, so meanwhile I was asked to do some testing work in a project. I've never done testing before, and there is no one to help me in that project. There is just me and my manager. So, I am the only one doing QA for this application. The application is being developed for the last 9 months, and I just started learning the application and testing by myself without any guidance. I've tested the application multiple times, atleast thrice daily, and found a lot of bugs. Now, that the application development is finished , the manager of the development team started scolding me saying that QA team(which has only me) not doing proper testing from a user point of view, and he is saying that he can find more bugs than me. And my manager says that if the application is released, and user finds new bugs, the company reputation will be spoiled and everyone will start blaming QA team.
I have no idea what's all this, but I feel pressurized. Can anyone suggest what should I do now ?
Quality(QA) is shared responsibility of the entire team. This needs to be realized by all. Sooner is better than later.
In the absence of formal software requirements, I would put together a basic test plan based on my understanding at least to define exit criteria to know what to test and when to stop. Then I would share & clarify the expectations from testing from all stakeholders. After lot of back & forth communication once all parties reach on same page, I will take their sign-off and complete testing in accordance to that plan religiously.
This might not go smooth and become bit chaotic however this has to happen at some point, sooner is better. This will give me something tangible to work upon and even if they disagree in some major way with my understanding of overall test requirements, this will be useful as a first stepping stone for starting off formal communication between all stake holders & reaching towards a consensus.
I would play more of a 'facilitator' in this conversation between stakeholders.
Effective testing is all about effective communication.