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 . BS – 2. Standard for Software Component Testing. Working Draft Date: 28 April produced by the. British Computer Society Specialist Interest. This paper covers both the development of BS and compliance with the finished standard. The process used to produce BS is described by.
|Published (Last):||2 June 2009|
|PDF File Size:||20.72 Mb|
|ePub File Size:||10.14 Mb|
|Price:||Free* [*Free Regsitration Required]|
Branch Condition Coverage uses a model of the component described in clause 3. The Standard therefore also includes the concept of measuring testing which has been done for a component as well as the assessment of whether testing met defined targets. Branch Condition Combination Coverage. This website is best viewed with browser version of up to Microsoft Internet Explorer 8 or Firefox 3.
Careers and apprenticeships Equal opportunities Vacancies Apprenticeships. Take the smart route to manage medical device compliance.
No coverage measure is defined for syntax testing. Categories are assigned to variable occurrences in the component, where the category identifies the definition or the use of the variable at that point. Later activities for one test case may occur before earlier activities for another. Statement testing uses a model of the source code which identifies statements as either executable or non-executable.
A complete strategy for all software testing would cover these and other aspects. These input and output values are derived from the specification of the component’s behaviour. Test cases with valid and invalid syntax are designed from the formally defined syntax of the inputs to the component. Software acquisition management experience learnt in a multi discipline and multi contract project environment.
Coverage items are unique combinations of the set of Boolean operand values within each decision condition. Branch Condition Combination Coverage is only defined for components with one entry point.
The definition of test case design techniques and measures provides for common understanding in both the specification and comparison of software testing.
The boundaries of both valid and invalid partitions are considered. University of Hong 79925-2. The objective of this Standard is to enable the measurement and comparison of testing performed on software components.
A working party was formed in January with a more formal constitution. This Standard defines a generic test process. Coverage items are decision outcomes. Before component testing may begin the component test strategy 2. All standards are subject to revision, and parties to agreements based on the Gs are encouraged to investigate the possibility of applying the most recent edition of the standard listed below.
BS 2 The Software Component Testing Standard – Technische Informationsbibliothek (TIB)
Given any initial state of the component, in a defined environment, for any fully-defined sequence of inputs and any observed outcome, it shall be possible to establish whether or not the component conforms to the specification. The states of the model shall be disjoint, identifiable and finite in number. For each identified boundary three test cases shall be produced corresponding to values on the boundary and an incremental distance either side of it.
For each test case, the following shall be specified: This Standard does not prescribe which test measurement techniques are to be used. The model shall comprise states, transitions, events, actions and their relationships.
Other test case design techniques may bx used that are not listed in this clause. A partition’s boundaries are normally defined by the values of the boundaries between partitions, however where partitions are disjoint the minimum and maximum values in the range which makes up the partition are used. For single transitions, the coverage metric is the percentage of all valid transitions exercised during test. Where no knowledge of this operational distribution is available then a uniform input distribution shall be used.
Test cases are designed to exercise partitions of valid values, and invalid input values.
The Test Management Guide – BS Standard for Software Component Testing
hs The objective shall be stated in terms of the 79252- case design technique being used, such as the partition boundaries exercised. Each effect is expressed as a Boolean expression representing an outcome, or a combination of outcomes, for the component having occurred.
The model is typically represented as a Boolean graph relating the derived input and output Boolean expressions using the Boolean operators: Cost-benefit data from a large-scale experiment on reinspection of a software requirements document.
The actual outcome shall be recorded. Each possible transfer of control is a decision outcome. Test cases shall be designed to exercise partitions. The control flow model for the component is derived and the location and category of variable occurrences on it identified. Data definition C-uses are all others, including variable occurrences in the right hand side of an assignment statement, or an output statement. Branch Condition Combination Coverage 4.
Test cases with invalid syntax shall be designed as follows: A test case may exercise any number of partitions. Computer software, Computer programs, Program testing, Computer applications, Performance testing, Software engineering techniques, Design, Quality assurance, Reports, Mathematical calculations, Boolean algebra, Acceptance approvalSyntax, Data transfer, Decision tables, Fitness for purpose, Bibliography Software engineering.
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. In each coverage calculation, a number of coverage items may be infeasible.
Some partitions may not have an identified boundary, for example, if a numerical partition has a lower but not an upper bound.