ISTQB Chapter 5 Testing Terms

  • Share this:
ISTQB Chapter 5 Testing Terms

Test management: The planning, estimating, monitoring, and control of test activities, typically carried out by a test manager. 

Tester: A skilled professional who is involved in the testing of a component or system. 

Test manager (test leader): The person responsible for project management of testing activities and resources, and evaluation of a test object. The individual who directs, controls, administers, plans, and regulates the evaluation of a test object. 

Configuration management: A discipline applying technical and administrative directions and surveillance to: identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements. 

Configuration control (version control): An element of configuration management, consisting of the evaluation, co-ordination, approval, or disapproval, and implementation of changes to configuration items after formal establishment of their configuration identification. 

Product risk: A risk directly related to the test object. 

Risk-based testing: An approach to testing to reduce the level of product risks and uniform stakeholders of their status, starting in the initial stages of a project. It involves the identification of product risks and the use of risk levels to guide the test process. 

Project risk: A risk related to management and control of the (test) project, e.g. lack of staffing, strict deadlines, changing requirements, etc. 

Incident management: The process of recognizing, investigating, taking action, and disposing of incidents. It involves logging incidents, classifying them, and identifying the impact. 

Incident logging: Recording the details of any incident that occurred, e.g. during testing. 

Defect report (bug report, problem report): A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function. 

Defect detection percentage (DDP): The number of defects found by a test phase, divided by the number found by that test phase and any other means afterwards. 

Incident report: Also known as deviation report. A document reporting on any event that occurred, e.g. during testing, which requires investigation. 

Priority: The level of (business) importance assigned to an item, e.g. defect. Severity: The degree of impact that a defect has on the development or operation of a component or system. 

Root cause: A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed. 

Test framework: 1) Reusable and extensible testing libraries that can be used to build testing tools (which are also called test harnesses); 2) A type of design of test automation (e.g. data-driven and keyword - driven); and 3) An overall process of execution of testing. 

Probe effect: The effect on the component or system by the measurement instrument when the component or system is being measured, e.g. by a performance testing tool or monitor. For example performance may be slightly worse when performance testing tools are being used.

Farhan Tanvir

Farhan Tanvir