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):||22 March 2009|
|PDF File Size:||3.99 Mb|
|ePub File Size:||3.12 Mb|
|Price:||Free* [*Free Regsitration Required]|
A sequence of one or more consecutive, executable statements containing no branches. Engineering a Secure Information Technology Organization. Retrieved 24 June The behavior actually produced when the object is tested under specified conditions.
Working Draft of BS
Component testing of individual component s in isolation b surrounding component s, with surrounding component s being simulated by stub s.
Bz component s are then used to test lower level component s. The diagrammatic representation of the possible alternative control flow paths through a component. The templates support the three primary test process levels of Part 2, and the standard also includes mapping to other existing standards. A sequence of executable statements within a component.
The process of testing that an implementation conforms to the specification on which it is based.
Vocabulaire Bw in German Software Pruefung. A description of a component ‘s function in terms of its output values for specified input values under specified precondition s. Retrieved 23 July A test case design technique for a component in which test cases are designed to execute branch outcomes.
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 percentage of path s in a component exercised by a test case suite.
Totalagreement will rarely, if ever, be achieved in compiling a document of this nature. The percentage of branch condition outcomes in every decision that have been exercised by a test case suite.
BS – Software testing. Vocabulary
Testing the ease with which users can learn and use a product. Learn more about the 79251- we use and how to change your settings. A variable whether stored within a component or outside it that is read by the component. A data definition and data usewhere the data use uses the value defined in the data definition. Some terms are preferred to other synonymous ones, in sb case, the definition of the preferred term appears, with the synonymous ones referring to that. The standard’s test design techniques are categorized into three main categories: See branch condition coverage.
A manifestation of an error in software. Coverage measures based on the internal structure of the component. Designing tests based on objectives derived from requirements for the software component e. 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 hs entry point of the component.
Testing aimed at verifying be system’s ability to recover from varying degrees of failure. Separation of responsibilities which ensures the accomplishment of objective evaluation.
A test case design technique for a component in which test cases are designed to execute statement s. An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level component s being simulated by stub s.
Your basket is empty. This standard covers keyword-driven testingan approach to specifying software tests normally automated used in the software testing industry. See equivalence partition testing. Testing of an object without execution on a computer.
The representation of selected behavioural characteristics of one physical or abstract system by another system. A test tool that records test input as it is sent to the software under test. A Linear Code Sequence And Jump, consisting of the following three items conventionally identified by line numbers in a source code listing: The process of exercising software to verify that it satisfies specified sb and to detect error s.
The percentage of decision outcomes that have been exercised by a test case suite. A skeletal or special-purpose implementation of a software module, used to develop or test a component that calls or is otherwise dependent on it. 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.
Accept and continue Learn more about the cookies we use and how to change your settings. Supporting information, such as the reason for a proposed change, or the reference to the use of a term. Designing bz based on objectives derived from the architectural or detail design of the software e. ISO standards by standard number.