Test Implementation

Profile picture for user devraj

Test Implementation is the process of developing and prioritizing test procedures, creating test data, and optionally, preparing test harnesses and writing automated test scripts. 

During test implementation, the testware necessary for test execution is created or completed. This testware includes sequencing the test cases into test procedures. Test Procedure is a sequence of test cases in execution order and any associated actions required to set up the initial preconditions and wrap-up activities post-execution.

Test Implementation answers the question, "do we now have everything in place to run the tests?" 

Test design and test implementation tasks are often combined. In the test implementation phase, the test team ensures that all the pre-requisites are handled to start the test execution.

In exploratory testing or another experience-based testing, test design and implementation may occur and be documented as part of test execution. In exploratory testing, tests are executed immediately as they are designed and implemented. 

Major activities of Test Implementation

  • Developing and Prioritizing Test Procedures. 
  • Preparing Test Harness (Stubs & Drivers)
  • Creating Automated Test Scripts
  • Creating Test Suites from Test Procedures. Where Test Suites are a collection of test cases. Test Suites are also known as Test Set in some Test management tools.
  • Arranging the test suites within a test execution schedule for efficient test execution. An execution schedule is a series of tasks or steps that can be run sequentially at a scheduled time. It is a scheme for the execution of test procedures. The test procedures are included in the test execution schedule in their context and in the order in which they are to be executed.
  • Building Test Environment and Verifying Everything needed has been set up correctly, including potentially test harnesses, service virtualization, simulators, and other infrastructure items.
  • Prepare the Test Data and ensure it is loaded in the test environment.
  • Verifying and updating bi-directional traceability between the test basis, test conditions, test cases, test procedures, and test suites