Chapter 12. Test Execution

Test execution is the phase held after the test strategies, test planning, test script documentation, and test procedures have been designed and developed. A testable software build is now ready to be deployed into the quality assurance (QA) environment. The main objective of test execution is to demonstrate that the actual test results for each test step match the expected test results. Alternatively, test execution may identify that the system configuration does not meet requirements, which causes the test team to log defects as discussed in Chapter 13.

Test execution is conducted after the test cases have been designed, documented, peer-reviewed, and approved, and the entrance criteria and/or test readiness review (TRR) have been evaluated. Test execution is conducted with either manual or automated test cases. For initial SAP implementations, test execution is conducted during the realization and final preparation phases. For existing SAP implementations, test execution is routinely held for regression testing that addresses system upgrades, addition of new SAP modules, SAP patches, OSS (Online Service System) notes, SAP hot packs, and production transports.

The construction of a test schedule prior to the start of the test execution is highly recommended to identify the sequence of dependencies in which the test cases need to be executed. A test schedule also helps to estimate the total time needed to execute all test cases associated with a testing ...

Get Testing SAP R/3: A Manager's Step-by-Step Guide now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.