Explain the pre testing phase, acceptance testing and testing phase.

Pre testing Phase:

1.      Review the requirements document for the testability: Tester will use the requirement document to write the test cases.

2.      Establishing the hard freeze date: Hard freeze date is a date after which system test team will not accept any more software and documentation changes from development team, unless they are fixes of severity 1 MR’s. The date is scheduled so that product test team will have time for final regression.

3.      Writing master test plan: It is written by the lead tester or test coordinator. Master test plan includes entire testing plan, testing resources and testing strategy.

4.      Setting up MR Tool: The MR tool must be set as soon as you know of the different modules in the product, the developers and testers on the product, the hardware platform, and operating system testing will be done.

This information will be available upon the completion of the first draft of the architecture document. Both testers and developers are trained how to use the system.

5.      Setting up the test environment: The test environment is set on separate machines, database and network. This task is performed by the technical support team.  First time it takes some time, Afterwards the same environment can be used by the later releases.

6.      Writing the test plan and test cases:  Template and the tool is decided to write the test plan, test cases and test procedures.  Expected results are organized in the test plan according to the feature categories specified in the requirement document.  For each feature positive and negative test cases are written.  Writing test plan requires the complete understanding of the product and its interfaces with other systems.  After test plan is completed, a walkthrough is conducted with the developers and design team members to baseline the test plan document.

7.      Setting up the test automation tool: Planning of test strategy on how to automate the testing. Which test cases will be executed for regression testing.  Not all the test cases will be executed during regression testing.

8.      Identify acceptance test cases: Select subsets that are expected on the first day of system test.  These tests must pass to accept the product in the system test.

 Acceptance testing phase:

1.      When the product enters system test, check it has completed integration test and must meet the integration test exit criteria.

2.      Check integration exit criteria and product test entrance criteria in the master test plan or test strategy documents.

3.      Check the integration testing sign off criteria sheet.

4.      Coordinate release with product development.

5.      How the code will be migrated from development environment to the test environment.

6.      Installation and acceptance testing.

Product testing phase:

1.      Running the test: Execution of test cases and verify if actual functionality of application matches the expected results.

2.      Initial manual testing is recommended to isolate unexpected system behavior. Once application is stable automated regression test could be generated.

3.      Issue MR’s upon detection of the bugs.

http://futurethoughtsllc.com/TestingandQA.aspx