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):||12 December 2011|
|PDF File Size:||19.70 Mb|
|ePub File Size:||20.85 Mb|
|Price:||Free* [*Free Regsitration Required]|
BS – Software testing. Vocabulary
From Wikipedia, the free encyclopedia. Examples are data definition-use coveragedata definition P-use coveragedata definition C-use coverageetc.
After [ Beizer ]. An entity or property used as a basis for testing. Systems, Software and Services Process Improvement: An input for which the specification predicts an outcome. 795-1
A path which cannot be exercised by any set of possible input values. Testing of new features after regression testing of previous features. An abstract representation of all possible sequences of events in a program’s execution.
Totalagreement will rarely, if ever, be achieved in compiling a document of this nature. The behaviour predicted by the specification of an object under specified conditions.
Views Read Edit View history. It comprises test process descriptions that define the software testing processes at the organizational level, test management project level, and dynamic test process levels WG26 couldn’t get consensus 77925-1 the inclusion of static testing. A manifestation of an error in software.
At the time of publication, the edition indicated was valid. A subpath of the control flow graph in which no program part is executed more than necessary.
Search all products by. A method used to measure test bd items. International Organization for Standardization. The method used to perform the actual test executione. Testing concerned with the accuracy of documentation. Standard Number BS Integration testing where no incremental testing takes place prior to all the system’s component s being combined to form the system.
Part 4 provides standard definitions of software test design techniques also known as test case design techniques or test methods and corresponding coverage measures that can be used during the test design and implementation processes defined in Part 2. The process of testing an integrated system to verify that it meets specified requirements.
The testing of individual software components. 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. The representation of selected behavioural characteristics of one physical or abstract system by another system. The process of intentionally adding known fault s to those already in a computer program for the purpose of monitoring the rate of detection and removal, and estimating the number of fault s remaining in the program.
Deviation of the software from its expected delivery or service. The document that describes in detail the characteristics of the product with regard to its intended capability. The percentage of equivalence classes generated for the componentwhich have been exercised by a test case suite. Retrieved from ” https: The percentage of data definition C-use pairs in a component that are exercised by a test case suite.
A sequence of executable statements within a component. The use of a term defined within this glossary is printed in italics. The percentage of path s in a component exercised by a test case suite. A test case design technique for a component in which test cases are designed to execute data definition-use pairs. 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.
A program that generates test cases in accordance to a specified strategy or heuristic.
A device, computer program or system used during software verification, which behaves or operates like a given system when provided with a set of controlled input s. Accept and continue Learn more about the cookies we use and how to change your settings.
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.