Test Entry Criteria and Test Exit Criteria

Test Entry Criteria

Test Planning Deliverables

1. Test Plan/Specification approved

2. Test Resources available

Code Readiness

1. Code complete for all requirements

2. Code changes migrated to environment and verified

3. Unit/Development testing activities completed and results available

Testing Environment Readiness

1. Environment and infrastructure properly installed and/or set up

2. Environment validation activity should be completed

3. No SEV1 or SEV2 defects from environment validation activity

Test Preparation Deliverables

1. Test Cases completed and available for review

2. Test Schedule completed

3. Test Management Tool set up with project’s information

4. Metrics Portal set up with project's information

Test Exit Criteria

Based on Defect Trend

1. No SEV1 or SEV2 defects - All the SEV1 or SEV2 defects MUST be in “Closed” , “Canceled”, “Duplicate” or “Rejected” status in the Test Management Tool. There should not be any Ready to Verify/Ready to Promote defects pending.        

2. All SEV3 and SEV4 defects are deferred - All the SEV3 and SEV4 defects which are not closed, should be moved to Deferred status.

Based on Testing Strategy

1. 100% test cases attempted - Test Scope is completed according to the Test Specification.

2. Above 90% planned test cases should be passed.

3. Failed test cases must have defect associated with it and defect severity should not be above SEV3 or SEV4.

Based on Evidences

1. Test Sign-off assessment result should be submitted for audit.

2. Test result should be available in Test management tool. 

What is the Difference between Verification & Validation?

Verification: Are we building the produce right?

It’s a static process which involves evaluation of project documents, requirements, code. Checklists are used to do the verification.

 Validation: Are we building a right Product?

Validation is actual testing where the product itself is tested with set of inputs and verify that it is working fine as per the requirement.

What is system testing?

After integrating all the modules the software is tested whether the entire system is working properly. All functional and non functional testing should be done under system testing. The software should be work as defined in the requirement document. 

Below mentioned testing types are considered under system testing:

Installation testing

Load testing

Performance testing

Smoke testing

Ad hoc testing

Regression testing

Exploratory testing

Security testing

What is the difference between static testing and dynamic testing?

Static Testing: In static testing is review the process using checklist, it involves code review, walkthrough, inspection. Static testing will be done before dynamic testing. The actual application or software will not be tested in this process.  

Eg. Code review

Dynamic Testing: In Dynamic testing the actual application is tested. Test cases are executed in this stage to find the defect.

Eg. Functional testing, system testing, integration testing etc

What is Software Testing?

Testing involves operation of a system or application under controlled conditions and evaluating the results. The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn't or things don't happen when they should.