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):||25 February 2017|
|PDF File Size:||11.51 Mb|
|ePub File Size:||1.29 Mb|
|Price:||Free* [*Free Regsitration Required]|
A test case design technique in which test cases are designed to execute path s of a component.
ISO/IEC – Wikipedia
Take the smart route to manage medical device compliance. The percentage of path s in a component exercised by a test case suite.
Designing tests based on objectives derived from requirements for the software component e. A software tool used to carry out instrumentation. The processing of a test case suite by the software under test, producing an outcome.
Testing in which test cases are designed based on variable usage within the code. Integration testing where the interfaces between system component s are tested.
Test case 795-1 that is based on an analysis of the internal structure of the component. Testing aimed at showing software does not work. A test tool that 79255-1 the actual output s produced by the software under test with the expected output s for that test case.
Working Draft of BS
This page was last edited on 23 Julyat See also branch outcomecondition outcome and decision outcome. Comments are invited on this draft so that the glossary can be improved to satisfy the requirements of an ISO standard.
A criterion for determining when planned testing is complete, defined in terms of a test measurement technique. These exploratory testing techniques rely on the experience of the human tester. A static analysis technique that derives a symbolic expression for program path s. 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 minimal software item for which a separate specification is available. These structural testing techniques are based on the internal structure of the system under test. Systems, Software and Services Process Improvement: Testing where the system is subjected to large volumes of data.
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. At the time of publication, the edition indicated was valid.
The set of all possible output s. For example dirty testing refers to negative testing. See non-functional requirements testing. This is the outcome of a test. Testing carried out using no recognised test case design technique.
Environmental and state conditions which must be fulfilled before the component can be executed with a particular input value. Stuart Reid, convenor of WG26, replied to some of these and other opposing viewpoints in September though it’s not clear if any further action by WG26 was taken due to software testers’ complaints.
See also error seeding. The insertion of additional code into the program in order to collect information about program behaviour during program execution.
They are also called white-box testing techniques. This standard covers keyword-driven testingan approach to specifying software tests normally automated used in the software testing industry. See functional test case design. The process of finding and removing the causes of failure s in software. A document providing detailed b for the execution of one or more test cases.
The process is repeated until the component at the top of the hierarchy is tested. The representation of selected behavioural bx of one physical or abstract system by another system. 7925- testing tool that comprises a test driver and a test comparator. Operational testing at a site not otherwise involved with the software developers. Designing tests based on objectives derived from the implementation e.
A variation of top-down testing where the progressive integration of component s follows the implementation of subsets of the requirements, as opposed to the integration of component s by successively lower levels. Simulated or actual operational testing at an in-house site not otherwise involved with the software 792-51. A human action that produces an incorrect result. Testing aimed at demonstrating the software can be ported to specified hardware or software platforms.