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):||1 February 2015|
|PDF File Size:||12.79 Mb|
|ePub File Size:||9.21 Mb|
|Price:||Free* [*Free Regsitration Required]|
The degree to which software conforms to its specification.
International Organization for Standardization. A test case design technique in which a model is used of the bd distribution of the input to construct representative test cases. An entity or property used as a basis for testing. A test case design technique in which test cases are designed to execute branch condition outcomes. A test case design technique for a component in which test cases are designed to execute data definition-use pairs. The last executable statement within a component. A minimal software item for which a separate specification is available.
From Wikipedia, the free encyclopedia. A sequence of executable statements within a component. Testing aimed at demonstrating the software can be ported to specified hardware or software platforms. Deviation of the software from its expected delivery or service. The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test case suite.
The process of sb an integrated system to verify that it meets specified requirements. Some terms are preferred to other synonymous ones, in which case, the definition of the preferred term appears, with the synonymous ones referring to that. A mechanism to produce the predicted outcomes to compare with 77925-1 actual outcomes of the software under test. A test case design technique for 7952-1 component in which bx cases are designed to execute representatives from equivalence classes.
A data definition and predicate data usewhere the data use uses the value defined in the data definition. For each test, an unambiguous record of the identities and versions of the component under test, the test specificationand actual outcome.
A review of requirements, designs or code characterized by the author of the object under review guiding the progression of the review. A document providing detailed instructions for the execution of one or more test cases.
A test case design technique for a component in which test cases are designed 79255-1 include representatives of boundary values. These exploratory bz techniques rely on the experience of the human tester. This is the outcome of a test. See also error seeding.
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. Computer software, Computer programs, Program testing, Computer applications, Performance testing, Software engineering techniques, Vocabulary Software engineering.
The faster, easier way to work with standards. The percentage of data definition P-use pairs in a component that are exercised by a test case suite. A test tool that compares the actual output s produced by the software under test with the expected output s for that test case. Determination of 792-1 c orrectness of the products of software development with respect to the user needs and requirements. An analysis method bbs determines which parts of the software have been executed covered by the test case suite and which parts have not been executed and therefore may require additional attention.
A program that generates test cases in accordance to a specified strategy or heuristic. You may experience issues viewing this site in Internet Explorer 9, 10 or See structural test case design.
792-51 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. Tested component s are then used to test lower level component s.
A skeletal or 792-51 implementation of a software module, used to develop or test a component that calls or is otherwise dependent on it. A test case design technique for a component or system in which test case design is based upon the syntax of the input.
Talk:BS – Wikipedia
Examples are data definition-use 792-51data definition P-use coveragedata definition C-use coverageetc. A method used to derive or select test cases. The testing of software by the manual simulation of its execution. A data definition and computation data usewhere the data use uses the value defined in the data definition. As of June [update]no major revisions have occurred to the five parts of the standard.
ISO/IEC – Wikipedia
Suggested test design techniques in this group are :. Designing tests based on objectives derived from requirements for the software component e. Coverage measures based on the internal structure of the component.
Choosing a set of input values to force the execution of a component to take a given path. The process of evaluating a system or component to determine whether the products of 79925-1 given development phase satisfy the conditions imposed at the start of that phase. At the time of publication, the edition indicated was valid. Testing concerned with the accuracy of documentation.
A collection of one or more test cases for the software under test.
Explicit use of et al. A subpath of the control flow graph in which no program part is executed more than necessary. Simulated or actual operational testing at an in-house site not otherwise involved with the software developers.
A statement which, when compiled, is translated into object code, which will be executed procedurally when the program is running and may perform an action on program data.