IPU BCA Semester 5: Testing Terminologies and Artifacts
Testing Terminologies and Artifacts
Test Harness: It is a small program written specifically to test a particular subroutine or module. It feeds data to the module under test and displays result. It usually has a GUI so that user can create data and put it under module being tested.
Test ware: Artifacts produced during test process such as documentations, scripts, expected results, test data environment and any additional software used in testing.
Test Basis: All documents from which the requirements of the system can be inferred and test cases are based.
Test Cases: The specification of test inputs, executions conditions, expected results, execution pre and post conditions developed to evaluate a particular test condition.
Test Script: It is a program used to automate test procedure specification.
Test Oracle: A source to determine expected result to compare with actual results obtained from software under test. Oracle can be requirements specification, manual or an individual's specialized knowledge but cannot be the code.
Test Data: Data that is used while testing a system/component/module.
Test Suite: Collection of test cases for a system where the post condition of one test is used as precondition for the next one.
Test Environment: An environment containing hardware ,instrumentation, simulators,,software tools and others supports elements needed to conducts a test.
Test Coverage: The extent to which the source code or modules of a program is/are involved during testing. It is measured in terms of the percentage of components or functions called during the test.
Test Driver: It is a set of modules that act as temporary replacement (called stubs) for a calling module and give the same output as that of the actual product.
Test Strategy: A static document prepared by the higher management of the testing team. The artifact defines the test objectives of all test stages and the techniques that apply.
Test Plan: A document that describes the scope, approach resources and schedule of intended test activities.
Traceability Matrix: Traceability Matrix is a document maintained in table format which correlates two documents and also gives the relationship between them. From software testing perspective, it links between software requirements and test cases.
