Levels of Test Execution Vs Test Cases | Manual Testing Tutorial PDF

Levels of Test Execution Vs Test Cases: -

Level 0: => P0 Test Cases (Basic Functionality)
Level 1: => All P0, P1 & P2 Test Cases
Level 2: => Selected P0, P1 & P2 Test Cases with respect to Modifications
Level 3: => Selected P0, P1 & P2 Test Cases with respect to bug density.
NOTE:
1. P0 priority Test cases indicate functionality testing, P1 priority test cases indicate non-functional testing & P2 test cases indicate usability testing.
2. Level – 0 (Sanity) on initial build
    Level – 1(Comprehensive) on suitable build.
    Level – 2(Regression) on modified build
    Level – 3(Final Regression/Post Mortem) on Master build.
         (User-Acceptance Testing) on Golden build.

Level 0 (Sanity Testing):

After the establishment with required software & Hardware then Testing Team conducts Sanity Testing to estimate Testability of that initial software build. If the initial build is not testable, then the Testing team rejects that
build & waits for suitable build to receive from developers. If the build is testable without any functionalities missing then the testing team concentrates on level 1 Real or Comprehensive Testing.
In this level 0 Sanity testing, the testing team estimates testability with the help of the below factors.
=> Understandability
=> Simplicity
=> Operatability
=> Observability
=> Consistency
=> Maintainable
=> Automatable (Optional)
=> Controllable
The combination of the above 8 factors is called testability. These 8 factors coverage on build estimates testability. The level 0 sanity testing is also known as smoke testing or testability testing or tester acceptance testing.

Level 1 (Comprehensive Testing):

After receiving stable build from developers the testing team concentrates on level 1 or comprehensive testing. In this stage, the testing arranges the dependent test cases as batches, every batch is also known as test suite or test set or test belt or test chain. After creating test batches, the test engineers execute case by case in every batch through manual testing or automated testing.
  
During test execution, either in manual or in automation, test engineers purpose test log document. This document consists of three types of entries.
=> Passed --- all expected values in test case are equal to actual values of build.
=> Failed --- anyone expected is varying with actual values of build.
=> Blocked – Test case execution postponed due to incorrect failed functionality
Test engineers prepare the above entries in test log for every test case in every test batch.
 
                                              Level 1 (Comprehensive) Test Cycle
From the above comprehensive test cycle diagram, the final status of every test case is that: Skip or Passed or Closed

Level 2 (Regression Testing):

During level 1 comprehensive testing the testing reports mismatches, if any to the development team defects reports. After accepting those defects, the developers perform changes in build coding and releases the modified build with release note. The testing on that modifies build to ensure completeness & correctness of the modifications in the build.

 In Level 2 Regression testing, the test engineers re-execute previously executes test on modified build to ensure modification. The selection of test cases to be re-executed depends upon the release note.
Identify resolved defect severity with respect to release with respect to release note of modified build.

 Case 1:
If the defect resolved by the development team is of high severity, the test engineers re-execute all P1 & carefully selected P2 Test case. On that modified build with respect to modification specified in release note.
Case 2:
If the defect resolved by the development team is of medium severity, then test engineers. Re-execute all P0, carefully selected P1 & some of P2 Test cases with respect to modification specified in release note.
Case 3:
If the defect resolved by the development team is low severity, then the test engineers re-execute some P0, some P1 & Some P2 Test cases on that modified build with respect to modifications specified in release note.
Case 4:
If the development team releases modified build due to sudden changes in requirements of customer then the test engineers execute all P0 & carefully selected P2 test cases Test cases on that modified build with respect to changes in
requirement.
In this level 2 Regression Testing, the testing people user two indicators for modified build: Check –In & Check – Out.