Ans: Unit test plan
Component integration test plan
System integration test plan
System test plan
Acceptance test plan

Ans: Two models are followed in documentation of requirements which are use case model and paragraph model. In paragraph model business requirements are written like a paragraph, which is old model. Nowadays all companies follow the use case model where the requirements are written by stating their clear objectives and explained with the help of screen shot.

Ans:  I am aware of how use cases look like and I can write if required. But I have never got an opportunity to write use cases because these are prepared by requirements gathering team. Anyhow I have reviewed the use cases of certain functionalities and have given my inputs for betterment of the same.

Ans: Sorry, I have never got the opportunity to work on white box testing.
Note: This is usually conducted by testers who have coding knowledge of the application under development.

Ans: Code coverage checks the percentage of code covered during test execution and test coverage checks the percentage of the tests that are executed during the test execution.

Ans: It will be assigned to a developer by development manger and developer will fix and move the bug to fixed status. We do retesting to check whether defect was fixed correctly. We also run regression tests for checking side effects due to fix.

Ans:  Metrics on reopen is usually collected by the development manager and he interacts appropriately with the developer. From my side, I might bring this to the test lead/ test manager’s notice just to make them aware that I am not able to complete verification of lots of bugs since many reopens are arising. If they feel it is necessary, they will discuss this with the development manager appropriately.

Ans:  It depends on the size of the organization and the risks involved. For large organizations with high risk projects, a serious management buy-in is required and a formalized QA processes necessary. For medium sized organization with lower risk projects, management and organizational buy-in, a slower, step-by-step process is required. For smaller group or projects, an adhoc process is more appropriate.

Ans: Common difficulties that test engineers face are:
Not up to date SRS: Changes made to the requirements may not be updated in SRS sometimes. So there will be a minor difference between the application developed and SRS. Since test cases are written and executed according to SRS certain bugs reported become invalid. Testers get to know about the changes in the requirement after reporting the bug during discussion with the development team.
Convincing the developer with respect to reported bugs and rejected bugs: Another challenge which I faced was to convince the developers regarding the bugs. I was successful most of the times in convincing the developers because I always explain the importance of fixing the bug from the business perspective and the customer’s point of view.

Delay in the release of Build: Sometimes build release may be delayed due to which detailed test coverage gets affected as less time is available.
In availability of discussion time: Some of the bugs require discussion before rejection so we need to buy some of the developer’s time. Due to time zone differences and busy schedules of the developer at times, discussions were prolonged for more than 2 weeks whereas they had to complete within 2 days as per SLA’s.

Ans:  I disagree with this since a test plan and test cases are very crucial for successful testing of the project. A test plan is crucial since;
A test plan provides clear objective of testing
A test plan document many things required during testing like communication method, bug tracking process, test stop criteria without which testing goal will not be fruitful
Test plans identify about risks and propose contingency plan much before and ensure issues are handled effectively.
Test cases are crucial since;
They guarantee that most important and commonly used conditions of end user are verified before the product is released.
Even a person with less exposure on the project can be involved in the test execution by following the test cases drafted by experience resources.