Terms of Software Testing (ISTQB) (S)

S.MART. goal methodology :

A methodology whereby objectives are defined very specifically rather than ...

safety :

The capability of the software product to achieve acceptable levels of risk ...

safety critical system :

A system whose failure or malfunetion may result in death or serious injury ...

safety testing :

Testing to determine the safety of a software product.

san ity test :

See smoke test

scalability :

The capability of the software product to be upgraded to accommodate inerea ...

scalability testing :

Testing to determine the scalability of the software product.

scenario testing :

See use case testing.

scorecard :

A representation of summarized performance measurements representing progre ...

scripting language :

A programming language in which executable test scripts are written, used b ...

SCRUM :

An iterative incremental framework for managing projects commonly used with ...

secu rity testi ng tool :

A tool that provides support for testing security characteristics and vulne ...

security testing :

Testing to determine the security of the software product. See also functio ...

security tool :

A tool that supports operational security.

Security  :

Attributes of software products that bear on its ability to prevent unautho ...

seri be :

The person who records each defect mentioned and any suggestions for proces ...

seripted testing :

Test execution carried out by following a previously documented sequence of ...

serviceability testing :

See maintainability testing.

session-based test management :

An approach to testing in which test activities are planned as uninterrupte ...

seve rity :

The degree of impact that a defect has on the development or operation of a ...

Shevvhart chart :

See control chart

short-circuiting :

A programming language/interpreter technique for evaluating compound condit ...

Simulation :

The representation of selected behavioral characteristics of one physical o ...

simulator :

A device, computer program or system used during testing, which behaves or ...

site acceptance testing :

Acceptance testing by users/customers at their site, to determine whether o ...

smoke test :

A subset of ali defined/planned test cases that cover the main functionalit ...

softvvare :

Computer programs, procedures, and possibly associated documentation and da ...

softvvare attack :

See attack.

Softvvare Failure Mode and Effect Analysis (SFMEA) :

See Failure Mode and Effect Analysis (FMEA).

Softvvare Failure Mode, Effects, and Criticality Analysis (SFMECA) :

See Failure Mode,Effects, and Criticality Analysis (FMECA).

Softvvare Fault Tree Analysis (SFTA) :

See Fault Tree Analysis (FTA).

softvvare feature :

See feature.

softvvare integrity level :

The degree to which software complies or must comply with a set of stakehol ...

softvvare lifecycle :

The period of time that begins when a software product is conceived and end ...

Softvvare Process İmprovement :

A program of activities designed to improve the performance and maturity of ...

softvvare product characteristic :

See quality attribute.

softvvare quality :

Thetotality of functionality and features of a software product that bear o ...

softvvare quality characteristic :

See quality attribute.

softvvare test incident :

See incident.

softvvare test incident report :

See incident report.

Softvvare Usability Measurement Inventory (SUMI) :

A questionnaire-based usability test technique for measuring software quali ...

source statement :

See statement.

specification :

A document that specifies, ideally in a complete, precise and verifiable ma ...

specification-based technique :

See black box test design technique.

specification-based test design technique :

See black box test design technique.

specification-based testing :

See black box testing.

specified input :

An input for which the specification predicts a result.

SPI :

See Software Process İmprovement.

stability :

The capability of the software product to avoid unexpected effects from mod ...

staged representation :

A model structure wherein attaining the goals of a set of process areas est ...

standard :

Formal, possibly mandatory, set of requirements developed and used to presc ...

Standard softvvare :

See off-the-shelf software.

standard-compliant testing :

Testing that complies to a set of requirements defined by a Standard, e.g., ...

standards testing :

See compliance testing.

state diagram :

A diagram that depicts the states that a component or system can assume, an ...

state table :

Agrid showingthe resulting transitions for each state combined with each po ...

state transition :

A transition between two states of a component or system.

state transition testing :

A black box test design technique in which test cases are designed to execu ...

statement :

An entity in a programming language, which is typically the smallest indivi ...

statement coverage :

The percentage of executable statements that have been exercised by a test ...

statement testing :

A white box test design technique in which test cases are designed to execu ...

static analysis :

Analysis of software development artifacts, e.g. requirements or code, carr ...

static analysis tool :

See static analyzer.

static analyzer :

A tool that carries out static analysis

static code analysis :

Analysis of source code carried out without execution of that software.

static code analyzer :

A tool that carries out static code analysis. The tool checks source code, ...

static testing :

Testing of a software development artifact, e.g., requirements, design or c ...

statistical testing :

A test design technique in which a model of the statistical distribution of ...

status accounting :

An element of configuration management, consisting of the recording and rep ...

STEP :

See Systematic Test and Evaluation Process.

storage :

See resource utilization.

storage testing :

See resource utilization testing.

stress testing :

A type of performance testing conducted to evaluate a system or component a ...

stress testing tool :

A tool that supports stress testing.

structural coverage :

Coverage measures based on the internal structure of a component or system.

structural test design technique :

See white-box test design technique.

structural testing :

See white-box testing.

structure-based technique :

See white-box test design technique.

structure-based test design technique :

See white-box test design technique.

structure-based testing :

See white-box testing.

structured vvalkthrough :

See walkthrough.

stub :

A skeletal or special-purpose implementation of a software component, used ...

subpath :

A sequence of executable statements within a component.

suitability :

The capability of the software product to provide an appropriate set of fun ...

suitability testing :

The process of testing to determine the suitability of a software product

SUMI :

See Software Usability Measurement Inventory.

suspension criteria :

The criteria used to (temporarily) stop ali or a portion of the testing act ...

syntax testing :

A black box test design technique in which test cases are designed based up ...

system :

A collection of components organized to accomplish a specific function or s ...

system integration testing :

Testing the integration of systems and packages; testing interfaces to exte ...

system of systems :

Multiple heterogeneous, distributed systems that are embedded in networks a ...

system testing :

The process of testing an integrated system to verify that it meets specifi ...

Systematic Test and Evaluation Process :

A structured testing methodology, also used as a content-based model for im ...