This paper covers both the development of BS and compliance with the finished standard. The process used to produce BS is described by. Download Citation on ResearchGate | On Jan 1, , S.C. Reid and others published BS The Software Component Testing Standard }. BS – 2. Standard for Software Component Testing. Working Draft Date: 28 April produced by the. British Computer Society Specialist Interest.
|Published (Last):||27 May 2015|
|PDF File Size:||10.57 Mb|
|ePub File Size:||10.78 Mb|
|Price:||Free* [*Free Regsitration Required]|
Test cases shall be designed to exercise values both on and next to the boundaries of the partitions. Test cases shall be designed to exercise rules, which define the relationship between the component’s inputs and outputs, where each rule corresponds to a unique possible combination of inputs to the component that have been expressed as Booleans.
The coverage calculation shall be defined as either counting or discounting infeasible items – this choice shall be documented in the test plan. Scientific Data Management Research Staff.
British Library Conference Proceedings Aims of the standard The most important attribute of this Standard is that it must be possible to say whether or not it has been followed in a particular case i.
This Standard addresses dynamic execution and analysis of the results of execution. This working draft of the Standard replaces all previous versions. For each identified boundary three test cases shall be produced corresponding to values on the boundary and an incremental distance either side of it. Data definition C-uses are all others, including variable occurrences in the right hand side of an assignment statement, or an output statement.
Accept and continue Learn more about the cookies we use and how to change your settings. Some partitions may not have an identified boundary, for example, if a numerical partition has a lower but not an upper bound. Data Flow Testing uses a model of the interactions between parts of a component connected by the flow of data as well as the flow of control. The history of the standard.
BS 2 The Software Component Testing Standard – Technische Informationsbibliothek (TIB)
Fault removal is a separate process to fault detection. Coverage items 792-2 decision outcomes. Each possible transfer of control is a decision outcome. The input and output values are derived from the specification of the component’s behaviour.
Syntax Testing uses a model of the formally-defined syntax of the inputs to a component. A software component must have a specification in order to be tested according to this Standard. No coverage measure is defined for random testing.
This shall include a description of the hardware and software environment in which all component the tests will be run. Browse subjects Browse through journals Browse through conferences. Any discrepancy found shall be logged and analysed in order bx establish where the error lies and the earliest test activity that should be repeated 79252 order to remove the discrepancy in the test specification or verify the removal of the fault in the component.
On the determination of an appropriate time for ending the software testing process. The model will typically be represented as a state transition diagram, state transition model, or a state table. Modified Condition Decision Coverage 4.
If a coverage item is discounted justification for its infeasibility shall be documented in the test records. Statement testing uses a model of the source code which identifies statements as either executable or non-executable. Coverage items are executable statements in the source code. This Standard does not prescribe who does the testing.
The following standard contains provisions which, through reference in this text, constitute provisions of the Standard. The Standard describes a number of techniques for test case design and measurement, which support the test process. Branch Condition Combination Coverage 4. Only appropriate techniques should be chosen and these will vary according to the software development environments and application domains. A working party was formed in January with a more formal constitution.
Test cases with valid and invalid syntax are designed from the formally defined syntax of the inputs to the component. Advanced Search Watchlist Search history Search help. You may experience issues viewing this site in Internet Explorer 9, 10 or Other test case design techniques may be used that are not listed in this clause. Decision Coverage is only defined for components with one entry point.
There are many challenges in software testing, and it would be easy to try and address too many areas, so the standard is deliberately limited in scope to cover only the lowest level of independently testable software. Test cases shall be chosen randomly from the input domain of the component according to the input distribution.
This is known as n – 1 switch coverage. Investigating the effect of a second software inspection cycle. Limit the search to the library catalogue. These attributes are selected to provide the means of assessing, comparing and improving test quality. Table of contents conference proceedings The table of contents of the conference proceedings is generated automatically, so it can be incomplete, although all articles are available in the TIB.
Because the interpretation of and name for the lowest level is imprecise, the term “component” has been chosen rather than other common synonyms such as “unit”, “module”, or “program” to avoid confusion with these more common terms and remain compatible with them.
This website is best viewed with browser version of up to Microsoft Internet Explorer 8 or Firefox 3.