The core ideas of software testing: principles, the test process, verification and validation, defects, and what makes testing independent and effective.
A test case without concrete (implementation level) values for input data and expected results. Logical operators are used: instances of the actual values are …
Any condition that deviates from expectation based on requirements specifications, design documents, user documents, standards, etc., or from someone's …
A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g., an incorrect statement or data …
An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes, it is hoped that the likelihood of …
A graphical representation used to organize and display the interrelationships of various possible root causes of a problem. Possible causes of a real or …
The set of generic and specific conditions, agreed upon with the stakeholders for permitting a process to be officially completed. The purpose of exit criteria …
A test case with concrete (implementation level) values for input data and expected results. Logical operators from high-level test cases are replaced by …
The percentage of all single condition outcomes that independently affect a decision outcome that have been exercised by a test case suite. 100% modified …
The total costs incurred on quality activities and issues and often split into prevention costs, appraisal costs, internal failure costs and external failure …
A content-based model for test process improvement built around twelve critical processes. These include highly visible processes, by which peers and management …
A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute …
The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms, e.g., …
The process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying them and identifying the impact.
A cross-functional team of stakeholders who manage reported defects from initial detection to ultimate resolution (defect removal, defect deferral, or report …
A procedure to derive and/or select test cases targeted at one or more defect types, with tests being developed from what is known about the specific defect …
A black-box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle, test cases are …
A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a …
The ratio of the number of failures of a given category to a given unit of measure, e.g., failures per unit of time, failures per number of transactions, …
The process of intentionally adding defects to a system for the purpose of finding out whether the system can detect, and possibly recover from, a defect. Fault …
A usability review technique that targets usability problems in the user interface or user interface design. With this technique, the reviewers examine the …
(1) The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. (2) The capability of the software …
A memory access failure due to a defect in a program's dynamic store allocation logic that causes it to fail to release memory after it has finished using it, …
Coordinated activities to direct and control an organization with regard to quality that include establishing a quality policy and quality objectives, quality …
The person who records each defect mentioned and any suggestions for process improvement during a review meeting, on a logging form. The scribe should ensure …
A document describing the approach, resources and schedule of intended review activities. It identifies, amongst others: documents and code to be reviewed, …
An approach to testing to reduce the level of product risks and inform stakeholders of their status, starting in the initial stages of a project. It involves …
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 …
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 …
A set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as …
The disproportionate growth of the number of test cases with growing size of the test basis, when using a certain test design technique. Test case explosion …
During the test closure phase of a test process data is collected from completed activities to consolidate experience, testware, facts and numbers. The test …
An item or event of a component or system that could be verified by one or more test cases, e.g., a function, transaction, feature, quality attribute, or …
A document specifying the test conditions (coverage items) for a test item, the detailed test approach and identifying the associated high-level test cases.
A plan for achieving organizational test process improvement objectives based on a thorough understanding of the current strengths and weaknesses of the …
A tool that provides support to the test management and control part of a test process. It often has several capabilities, such as testware management, …
A five-level staged framework for test process improvement, related to the Capability Maturity Model Integration (CMMI), that describes the key elements of an …
A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be …
The fundamental test process comprises test planning and control, test analysis and design, test implementation and execution, evaluating exit criteria and …
A statement that echoes the Agile manifesto, and defines values for improving the testing process. The values are: flexibility over detailed processes, best …
A group of test activities aimed at testing a component or system focused on a specific test objective, i.e. functional test, usability test, regression test …
Artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, inputs, expected results, set-up and …
A tool that provides an environment for unit or component testing in which a component can be tested in isolation or with suitable stubs and drivers. It also …
Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.