| Item |
Description |
| Safety testing |
The process of testing to determine the safety of a software product. |
| Scalability |
The capability of the software product to be upgraded to accommodate increased loads. |
| Schedule |
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. |
| Scribe |
The person who has to record each defect mentioned and any suggestions for improvement during a review meeting, on a logging form. The scribe has to make ensure that the logging form is readable and understandable. |
| Script |
Commonly used to refer to a test procedure specification, especially an automated one. |
| Security |
Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data. |
| Severity |
The degree of impact that a defect has on the development or operation of a component or system. |
| Simulation |
The representation of selected behavioral characteristics of one physical or abstract system by another system. |
| Using a model to mimic a process. |
| Simulator |
A device, computer program or system used during testing, which behaves or operates like a given system when provided with a set of controlled inputs. |
| Smoke test |
A subset of all defined/planned test cases that cover the main functionality of a component or system, to ascertaining that the most crucial functions of a program work, but not bothering with finer details. |
| A daily build and smoke test is among industry best practices. |
| Stability |
The capability of the software product to avoid unexpected effects from modifications in the software. |
| State diagram |
A diagram that depicts the states that a component or system can assume, and shows the events or circumstances that cause and/or result from a change from one state to another. |
| State table |
A grid showing the resulting transitions for each state combined with each possible event, showing both valid and invalid transitions. |
| State transition testing |
A black box test design technique in which test cases are designed to execute valid and invalid state transitions. |
| Statement |
An entity in a programming language, which is typically the smallest indivisible unit of execution. |
| Statement coverage |
The percentage of executable statements that have been exercised by a test suite. |
| Statement testing |
A white box test design technique in which test cases are designed to execute statements. |
| Static analysis |
Analysis of software artifacts, e.g. requirements or code, carried out without execution of these software artifacts.
|
| Statistical testing |
A test design technique in which a model of the statistical distribution of the input is used to construct representative test cases. |
| Strategy |
A high-level document defining the test levels to be performed and the testing within those levels for a programme (one or more projects). |
| Stress testing |
Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements. |
| Structural coverage |
Coverage measures based on the internal structure of the component. |
| Stub |
A skeletal or special-purpose implementation of a software component, used to develop or test a component that calls or is otherwise dependent on it. It replaces a called component. |
| Subgoal |
An attribute which becomes a temporary intermediate goal for the inference engine. Subgoal values need to be determined because they are used in the premise of rules that can determine higher level goals. |
| Suitability |
The capability of the software product to provide an appropriate set of functions for specified tasks and user objectives |
| Suspension criteria |
The criteria used to (temporarily) stop all or a portion of the testing activities on the test items. |
| Symbolic Processing |
Use of symbols, rather than numbers, combined with rules-of-thumb (or heuristics), in order to process information and solve problems. |
| Syntax testing |
A black box test design technique in which test cases are designed based upon the definition of the input domain and/or output domain. |
| System |
A collection of components organized to accomplish a specific function or set of functions. |
| System integration testing |
Testing the integration of systems and packages; testing interfaces to external organizations (e.g. Electronic Data Interchange, Internet). |
