Glossary of Terms beginning Alphabet-T
Table coverage is a metric, which indicates whether each entry in a particular array has been referenced. This is useful for programs, which are controlled by a finite state machine.
Technical Review refers to a peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. A technical review is also known as a peer review.
Test is an activity in which a system or component is executed under specified conditions, the results are observed or recorded and an evaluation is made of some aspect of the system or component.
Testability is the capability of the software product to enable modified software to be tested. It is a quality attribute pointing towards an effort required in testing a program to ensure that it performs in accordance with its intended function. It is the degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.
Testability Review is a detailed check of the test basis to determine whether the test basis is at an adequate quality level to act as an input document for the test process.
Testable Requirements is the degree to which a requirement is stated in terms that permit establishment of test designs (and subsequently test cases) and execution of tests to determine whether the requirements have been met.
Tester is a technically skilled professional who is involved in the testing of a component or system.
Testing is the process consisting of all life cycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
Testware refers to the artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, inputs, expected results, set-up and clear-up procedures, files, databases, environment, and any additional software or utilities used in testing.
Test Approach is the implementation of the test strategy for a specific project. It typically includes the decisions made that follow based on the (test) project�s goal and the risk assessment carried out, starting points regarding the test process, the test design techniques to be applied, exit criteria and test types to be performed.
Test Automation refers to the use of software to perform or support test activities, e.g. test management, test design, test execution and results checking.
Test Basis refers to all documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be amended only by way of formal amendment procedure, then the test basis is called a frozen test basis.
Test Bed is an execution environment configured for testing. It may consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project enumerates the test beds(s) to be used.
Test Case is a commonly used term for a specific test. Test Case is a document which carries the detailed information pertaining to the inputs, expected results, and execution conditions of a defined test item to verify compliance with a specific requirement.
Test Case Generator:
Test Case Generator is a software tool that accepts as input source code, test criteria, specifications, or data structure definitions; uses these inputs to generate test input data; and, sometimes, determines expected results.
Test Case Specification:
Test Case Specification is a document specifying a set of test cases (objective, inputs, test actions, expected results, and execution preconditions) for a test item.
Test Charter is a statement of test objectives, and possibly test ideas. Test charters are amongst other used in exploratory testing. See also exploratory testing.
Test Comparator is a test tool to perform automated test comparison.
Test Comparison is the process of identifying differences between the actual results produced by the component or system under test and the expected results for a test. Test comparison can be performed during test execution (dynamic comparison) or after test execution.
Test Condition is an item or event of a component or system that could be verified by one or more test cases, e.g. a function, transaction, quality attribute, or structural element.
Test Data is the data, which exists (for example, in a database) before a test is executed, and that affects or is affected by the component or system under test.
Test Data Preparation Tool:
Test Data Preparation Tool is a type of test tool that enables data to be selected from existing databases or created, generated, manipulated and edited for use in testing.
Test Design is a set of documentation specifying the details of the test approach for a software feature or combination of software features and identifying the associated tests. See: testing functional; cause effect graphing; boundary value analysis; equivalence class partitioning; error guessing; testing, structural; branch analysis; path analysis; statement coverage; condition coverage; decision coverage; multiple-condition coverage.
Test Design Specification:
Test Design Specification is a document specifying the test conditions (coverage items) for a test item, the detailed test approach and identifying the associated high level test cases.
Test Design Tool:
Test Design Tool is a tool which support the test design activity by generating test inputs from a specification that may be held in a CASE tool repository, e.g. requirements management tool, or from specified test conditions held in the tool itself.
Test Design Technique:
Test Design Technique is a method used to derive or select test cases.
Test Documentation is a set of documents describing plans for, or results of, the testing of a system or component, Types include test case specification, test incident report, test log, test plan, test procedure, test report.
Test Driven Development:
Test Driven Development refers to testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.
Test Driver is a software module used to invoke a module under test and, often, provide test inputs, control and monitor execution, and report test results. It is also known as a Test Harness.
Test Environment refers to the hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.
Test Evaluation Report:
Test Evaluation Report is a document produced at the end of the test process summarizing all testing activities and results. It also contains an evaluation of the test process and lessons learned.
Test Execution is the process of running a test by the component or system under test, producing actual result(s).
Test Execution Automation:
Test Execution Automation is the use of software, e.g. capture/playback tools, to control the execution of tests, the comparison of actual results to expected results, the setting up of test preconditions, and other test control and reporting functions.
Test Execution Phase:
Test Execution Phase is the period of time in a software development life cycle during which the components of a software product are executed, and the software product is evaluated to determine whether or not requirements have been satisfied.
Test Execution Schedule:
Test Execution Schedule 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.
Test Execution Technique:
Test Execution Technique is the method used to perform the actual test execution, either manually or automated.
Test Execution Tool:
Test Execution Tool is a type of test tool that is able to execute other software using an automated test script, e.g. capture/playback.
Test First Design:
Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.
Test Harness is a program or test tool used to execute a tests. Also known as a Test Driver.
Test Incident Report:
Test Incident Report is a document reporting on any event that occurs during testing that requires further investigation.
Test Infrastructure is the organizational artifacts needed to perform testing, consisting of test environments, test tools, office environment and procedures.
Test Item is the individual software item, which is the object of testing. There usually is one test object and many test items.
Testing is the process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component. In software engineering parlance it is the process of Locating or Identifying the errors or bugs in a software system. It must clearly differentiated from “Debugging” which refers to process of rectifying the syntax errors, logic errors and all other types of errors identified during the process of testing.
Test Level is a group of test activities that are organized and managed together. A test level is linked to the responsibilities in a project. Examples of test levels are component test, integration test, system test and acceptance test.
Test Log is a chronological record of all relevant details about the execution of a test.
Test Logging is the process of recording information about tests executed into a test log.
Test Manager is the person responsible for testing and evaluating a test object. The individual, who directs, controls, administers plans and regulates the evaluation of a test object.
Test Management is the process of planning, estimating, monitoring and control of test activities, typically carried out by a test manager.
Test Maturity Model or TMM:
Test Maturity Model or TMM is a five level staged framework for test process improvement, related to the Capability Maturity Model (CMM) that describes the key elements of an effective test process.
Test Object is the component or system to be tested. See also test item.
Test Objective refers to the reason or purpose for designing and executing a test.
Test Oracle is a source to determine expected results to compare with the actual result of the software under test. An oracle may be the existing system (for a benchmark), a user manual, or an individual�s specialized knowledge, but should not be the code.
Test Performance Indicator:
Test Performance Indicator is a metric, in general high level, indicating to what extent acertain target value or criterion is met. Often related to test process improvement objectives, e.g. Defect Detection Percentage (DDP).
Test Phase is the period of time in the software life cycle in which the components of a software product are evaluated and integrated, and the software product is evaluated to determine whether or not requirements have been satisfied. It is a distinct set of test activities collected into a manageable phase of a project, e.g. the execution activities of a test level.
Test Plan is a document describing an introduction to the client company, intended scope, overview of the application, test strategy, schedule of testing activities, roles and responsibilities, deliverables and milestones and any risks requiring contingency planning. It describes test items, features to be tested, testing tasks, details of the personnel performing each task and any risks requiring contingency planning. As a summary; Test plan is a Document usually developed by the Test Lead & it contains information like “What to Test”, “How to Test”, “When to Test” & “Who is going to Test”.
Test Planning refers to the activity of establishing or updating a test plan.
Test Policy is a high level document describing the principles, approach and major objectives of the organization regarding testing.
Test Point Analysis or TPA:
Test Point Analysis or TPA is a formula based test estimation method based on function point analysis.
Test Procedure is a formal document developed from a test plan which provides detailed instructions for the setup, operation and evaluation of the results of one or more Test Cases.
Test Procedure Specification:
Test Procedure Specification is a document specifying a sequence of actions for the execution of a test. It is also known as test script or manual test script.
Test Process is the fundamental test process comprises planning, specification, execution, recording and checking for completion.
Test Process Improvement or TPI:
Test Process Improvement or TPI is a continuous framework for test process improvement that describes the key elements of an effective test process, especially targeted at system testing and acceptance testing.
Test Readiness Review:
Test Readiness Review is a review conducted to evaluate preliminary test results for one or more configuration items; to verify that the test procedures for each configuration item are complete, comply with test plans and descriptions, and satisfy test requirements. The aim is to verify that a project is prepared to proceed to formal testing of the configuration items. It is in contrast with code review, design review, formal qualification review, requirements review.
Test Report is a document describing the conduct and results of the testing carried out for a system or system component.
Test Result Analyzer:
Test Result Analyzer is a software tool used to test output data reduction, formatting, and printing.
Test Repeatability is an attribute of a test indicating whether the same results are produced each time the test is executed.
Test Run refers to the process of execution of a test on a specific version of the test object.
Test Script is commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool. It specifies an order of sequential actions that should be performed during a test session. It contains expected results as well. Test scripts may be prepared manually using paper forms, or may be automated using capture / playback tools or other kinds of automated scripting tools.
The term “Test Scenario” & “Test Cases” are often used synonymously. Test Scenario are nothing but Test Cases or Test Scripts having the sequence in which they are to be executed. Test Scenario are Test Cases which ensures that all business process flows are tested from end to end. Test Scenario are independent tests, or a series of tests that follow each other , where each of them is dependent upon the output of the previous one. Test Scenarios are prepared by reviewing functional requirements, and preparing logical groups of functions that can be further broken into test procedures. Test Scenarios are designed to represent both typical & unusual situations that may occur in an application.
Test Specification is a document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.
Test Strategy Is a high-level document, usually developed by the Project Manager & it contains information like what type of technique to be followed and which module to be tested.
Test Summary Report:
Test Summary Report is a document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria.
Test Suite is a collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.
Test Suite Manager:
Test Suite Manager is a tool, which allows testers to organize test scripts either by function or by any other way of grouping.
Test Target is a set of exit criteria.
Test Tool is a software product that supports one or more test activities, such as planning and control, specification, building initial files and data, test execution and test analysis.
Test Type is a group of test activities aimed at testing a component or system regarding one or more interrelated quality attributes. A test type is focused on a specific test objective, i.e. reliability test, usability test, regression test etc., and may take place on one or more test levels or test phases.
Thread Testing is a variation of Top-Down-Testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.
Top Down Testing:
Top Down Testing is an incremental approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.
Total Quality Management:
Total Quality Management is a company commitment to develop a process that achieves high quality product and customer satisfaction.
Traceability is the ability to identify related items in documentation and software, such as requirements with associated tests.
Traceability Matrix is a document showing the relationship between Test Requirements and Test Cases.