Guidelines for Test Execution

 Verifying and validating the pre-decided requirements.

 The build (a standalone application)
 Three phases:
 creation of test strategy and cases.
 execution of test cases
 validation of test results.
 QA test environment
 Development
 Testing
 Staging
 Production
 Select the BEST test suites
 highly-skilled software testers
 Test Execution cycle
 Test Readiness Review
 Exploratory testing

 Smoke and Sanity testing

 Output of the execution of test cases

 Teams can execute tests manually or by leveraging automation tools.

What aspects to consider during Test Execution

 Make sure the test design and test case creation are completed.
 Select a subset of the test suite for this cycle based on risk.
 For each test suite, assign test cases to testers.
 Track test status, execute tests, and report bugs continuously.
 Identify and resolve blocking issues as they arise.
 Report daily statuses, adjust assignments, and reevaluate priorities.
  Analyze and report findings from the test cycle.

Test Execution States

The following are some of the most critical execution states and their classifications.

 Pass
 Fail
 Inconclusive
 Block
 Deferred
 In Progress
 Not run

Test Priorities
The following is a list of variables that have been found to influence Test
Execution priority:

 Risks covered
 Platforms covered
 Test complexity
 Test case depth
 Test case breadth

Test Execution Cycle

The Software testing life cycle consists of six different phases.

 Requirement analysis
 Test planning
 Test case designing and development
 Test environment setup
 Test execution
 Test closure