Document of Understanding

Software Testing Life Cycle:

A systematic approach to test a software.

Test planning:
Test Planning includes two major parts, they are

1. Test strategy – Mangers will prepare this part.

2. Test plan – Team Leads will prepare this Test Artifact. The various sections available

in Test plan are as below:

Test Plan:
The Test plan is a document which will describe about what to test ,when test and how to
test. It also includes testing approach.

2.1 Introduction – Overview about test plan.

2.2 Reference Documents – contains the details of reference documents that used to

prepare test plan.

2.3 Intended Audience - Stockholders who all are referring the Test plan document.

Eg: Testing team, development team, clients and onsite team.

2.4 Definitions and Acronyms – provides details about definitions and acronyms that

are used in the Project

2.5 Features/items to be tested – includes items which are going to be tested.

2.6 Features/items not to be tested – includes items that not going to be tested.

2.7 Test Environment - Explains about hardware and software requirements. It is also

called as Test Bed.

2.8 Types of testing->This section explains about types of testing(Eg.

System,Integration, regression testing…) which has to be performed in the

project.

2.9 Risks and mitigation plan – Analyze risk factors in testing and providing

troubleshooting procedures(Mitigation plan)

2.10 Test deliverable

2.10.1 Pre testing – tells about the Test Artifacts that going to be delivered before

performing testing.

It includes

a. Test strategy, test plan, test case without filled results, test data and

test scripts.

2.10.2 Post testing - tells about the phases that going to done after testing.

It includes test cases with filled, final test report and defect report.

2.11 Milestone – provides start date and end date of Testing activities.

2.12 Entry and exit criteria.

2.13 Testing tools – Automation tools(Eg.Selenium..)

2.14 Defect management-Defect tracking tool information(Bugzilla or JIRA…)

& defect status

2.15 Roles and responsibility – includes the roles and responsibilities of the

Testing team members.

Entry and Exit criteria:

 Levels of Testing:

Entry criteria:

1. Unit Test cases should be prepared , reviewed and approved

2. Unit Test data should be available

3. Unit Test environment should be available

Unit testing

Exit criteria

1. All the unit testcases should be successfully executed i.e 1 round of unit

testing has to be performed

2. No major unit testing defects

Entry criteria:

1. All the unit testcases should be successfully executed i.e 1 round of unit

testing has to be performed

2. No major unit testing defects

3. Integration test cases should be prepared, reviewed and approved.

4. Integration test data should be available

5. Integration test environment should be available

Integration testingte
Exit criteria:

1. All integration test cases should be executed..i.e 1 round of integration

testing should be successfully completed

2. No major integration testing defects

Entry criteria:

1. All integration test cases should be executed..i.e 1 round of integration

testing should be successfully completed

2. No major integration testing defects

3. System test cases should be prepared, reviewed and approved

4. System test data should be available

5. System test environment should be available

System testing

1. All system test cases should be executed

2. No major system testing defects

4. User acceptance testing