This BS article has very limited content, and this standard has now been superseded by ISO/IEC/IEEE – so what little is here, is obsolete anyway . Find the most up-to-date version of BS at Engineering Purchase your copy of BS as a PDF download or hard copy directly from the official BSI Shop. All BSI British Standards available online in.
|Published (Last):||2 October 2007|
|PDF File Size:||14.9 Mb|
|ePub File Size:||4.59 Mb|
|Price:||Free* [*Free Regsitration Required]|
In compiling this glossary the committee has sought the views and comments of as broad a spectrum of opinion as possible in industry, commerce and government bodies and organisations, with the aim of producing a standard which would gain acceptance in as wide a field as possible.
79225-1 will rarely, if ever, be achieved in sb a document of this nature. Moreover, the professional, or technical use of these terms is often at variance with the meanings attributed to them by lay people. This document presents concepts, terms and definitions 7952-1 to aid communication in software testing and related disciplines. The glossary has been arranged in a single section of definitions arranged alphabetically. The use of a term defined within this glossary is printed in italics.
Some terms are preferred to other synonymous ones, in which case, the definition of the preferred term appears, with the synonymous ones referring to that. For example dirty testing refers to negative testing. At the time of publication, the edition indicated was valid.
All standards are subject to revision, and parties to agreements based upon this Standard are encouraged to investigate the possibility of applying the most recent edition of the standards listed below. Data processing – Vocabulary – Part Method of defining Syntactic Meta language. Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a system or component.
The behavior actually produced when the object is tested under specified conditions. Testing carried out using no recognised test case design technique. Simulated or actual operational testing at an in-house site not otherwise involved with the software developers. A meta language used to formally describe the syntax of a language.
A sequence of one or more consecutive, executable statements containing no branches. The combination of input values and precondition s and the required response for a function of a system. The full specification of a function would normally comprise one or more behaviour s. Operational testing at a site not otherwise involved with the software developers. Integration testing where no incremental testing takes place prior to all the system’s component s being combined to form the system.
An approach to integration testing where the lowest level component s are tested first, then used to facilitate the testing of higher level component s. The process is repeated until the component at the top of the hierarchy is tested. An input value or output value which is on the boundary between equivalence classesor an incremental distance either side of the boundary. A test case design technique for a component in which test cases are designed which include representatives of boundary values.
The percentage of boundary values of the component’s equivalence classes which have been exercised by a test case suite. See boundary value analysis. A conditional transfer of control from any statement to any other statement in a componentor an unconditional transfer of control from any statement to any other statement in the component except the next statementor when a component has more than one entry pointa transfer of control to an entry point of the component.
The percentage of combinations of all branch condition outcomes in every decision that have been exercised by a test case suite. A test case design technique in which test cases are designed to execute combinations of branch condition outcomes. The percentage of branch condition outcomes in every decision that have been exercised by a test case suite. A test case design technique in which test cases are designed to execute branch condition outcomes. The percentage of branches that have been exercised by a test case suite.
A test case design technique for a component in which test cases are designed to execute branch outcomes. A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. A graphical representation of inputs or stimuli causes with their associated outputs effectswhich can be used to design test cases.
A 7925- case design technique in which test cases ns designed by consideration of cause-effect graphs. The process of confirming that a system or component complies with its specified requirements and is acceptable for operational use. An analysis method that determines which parts of the software have been executed covered by the test case suite and which parts have not been executed and therefore may require additional attention.
Designing tests based on objectives derived from the implementation e. Testing whether the system is compatible with other systems with which it should communicate. A minimal software item for which a separate specification is available. The testing of individual software 79255-1.
A data use ba in a condition. A Boolean expression containing no Boolean operators. See branch condition coverage. Some method of judging whether or not the component ‘s action on a particular specified input value conforms to the specification. The process of testing that an implementation conforms to the specification on which it is based. An abstract representation of all possible sequences of events in a program’s execution.
The diagrammatic representation of the 79251- alternative control flow paths through a component.
Bz of programs or procedures used to convert data from existing systems for use in replacement systems. The degree to which software conforms to its specification. The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test case suite. An entity or property used as a basis for testing. An executable statement where a variable is assigned a value.
The percentage of data definition C-use pairs in a component that are exercised by a test case suite. A data definition and computation data usewhere the data use uses the value defined in the data definition. The percentage of data definition P-use pairs in a component that are exercised by a test case suite. A data definition and predicate data usewhere the data use uses the value defined 79225-1 the data definition. The percentage of data definition-use pairs in a component that are exercised by a test case suite.
A data definition and data usewhere the data use uses the value defined in the data definition. A test case design technique for a component in which test cases are designed to execute data definition-use pairs. Test coverage gs based on variable usage within the code. Examples are data definition-use coveragedata definition P-use coveragedata definition C-use coverageetc.
BS – Software testing. Vocabulary
Testing in which test cases are designed based on variable usage within the code. An executable statement where the value of a variable is accessed. The process of finding and removing the causes of failure s in software. A program point at which the control flow has two or more alternative routes. A condition ns a decision. The percentage of decision outcomes that have been exercised by a test case suite. The result of a 9725-1 which therefore determines the control flow alternative taken.
Designing tests based on objectives derived from the architectural or detail design of the software e. The testing of software by the manual bz of its execution. Testing concerned with the accuracy of documentation.
See equivalence partition testing. The process of evaluating a 7295-1 or component based upon its behaviour during execution. A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system. The first executable statement within a component.
A portion of the component ‘s input or output domains for which the component ‘s behaviour is assumed to be the same from the component’ s specification. The percentage of equivalence classes generated for the componentwhich have been exercised by a test case suite.
A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes. A human action that produces an incorrect result. A test case design technique where the experience of the tester is used to postulate what faults might occur, and to design tests specifically to expose them. The process of intentionally adding known fault s to those already in a computer program for the purpose of monitoring the rate of detection 9725-1 removal, and estimating the number of 77925-1 s remaining in the program.
A statement which, when compiled, is translated into object code, which will be executed procedurally when the program is running and may perform an action on program data. A program element is exercised by a test case when the input value causes the execution of that element, such as a statementbranch, or other structural element.
A test case design technique in which the test case 79225-1 comprises all combinations of input values and precondition s for component variables. The last executable statement 79255-1 a component.
Deviation of the software from its expected 7952-1 or service. A manifestation of an error in software. A faultif encountered may cause a failure.
A path for which there exists a set of input values and execution conditions which causes it to be executed. The document that describes in detail the characteristics of the product with regard to its intended capability. Test case selection that is based on an analysis of the specification of the component without reference to its internal workings.
See structural test case design.
Integration testing where system component s are integrated into the system one at a time until the entire system is integrated. Separation of responsibilities which ensures the accomplishment of objective evaluation.