PA 2.4 SG 3 – Perform test execution

Perform all activities according to planned test execution.


This Specific Goal looks to ensure that tests are executed according to previously specified test procedures and a published test schedule. Also that incidents (defects) are reported and test logs are written.

Specific Practices

SP 3.1 Perform intake test

Ensure that the test activities validate the test environment, application build and other elements of preparation by executing the intake test. If not successful, then that test level / activity / cycle is suspended as it is not valid (normally) to execute tests against a deficient environment (it causes erroneous results). This is closely aligned with SP2.4 of the “test environments” Process Area and can be combined.

SP 3.2 Execute test cases

We look to demonstrate that tests are executed in the correct order in accordance with the test plans and schedules, that test logs are maintained, providing the required level of information.

SP 3.3 Report test incidents

Any defects are raised in accordance with a defined procedure and work flow.

SP 3.4 Write test log

Part of this may also look to demonstrate that test progress summary reporting is undertaken as the test level / cycle / activity progresses.

Deployment notes

  • Is the test environment and application verified as ready for test execution to commence according to defined intake test procedures?
  • Are results and issues logged?
  • Are test cases executed according to the test execution schedule and results (actual versus expected, etc.) logged?
  • Is re-test undertaken after issues are appropriately fixed?
  • Is regression testing identified and undertaken according to an appropriate approach?
  • Are test incidents recorded, analysed and fixed according to a defined work flow and using a central repository?
  • Is there adequate use of categories and classifications?
  • Are all required stakeholders involved as appropriate?
  • Are adequate records of test execution activities and results maintained in test logs?