Software Testing Artifacts

Software testing process can produce the following artifacts.

Test plan

Firstly, a test specification is a test plan. The developers are conscious of what test plans will execute and this information is given to management and the developers. In other words, the idea is to make developers more aware and conscious while developing their code or making necessary changes to ensure that the product meets its design specifications and other requirements.

Traceability matrix

Secondly, a traceability matrix is a table that corresponds to requirements to test documents. It changes tests when there is a chance is source documents or to verify that the results are correct.

Test case

After that, a test case usually comprises a unique identifier, requirement references from a design specification, preconditions, events, and a series of steps to follow, input, output, expected result, and actual result. Larger test cases may also contain prerequisite steps and descriptions.

Test script

The test script refers to the combination of a test case, test procedure, and test data. Test scripts can be manual, electronic, or a combination of both. Most importantly, it is a set of instructions perform to test the system functions.

Test suite

The most common term for a compendium of test cases is a test suite. Further, the test suite contains instructions and details in more detail for each collection of test cases.

Test data

In most cases, multiple sets of data tests the same functionality of a particular feature. All the test values and changeable environmental components are collected in separate files and stored as test data.

Test harness

Lastly, test harness incorporates software, tools, samples of data input and output, and configurations.

Get certified and unlock more opportunities. Practice and Validate your skills to become a Certified Agile Testing Professional Now