[1988] Proceedings. Second Workshop on Software Testing, Verification, and Analysis
DOI: 10.1109/wst.1988.5371
|View full text |Cite
|
Sign up to set email alerts
|

A practical method for software quality control via program mutation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 11 publications
(6 citation statements)
references
References 7 publications
0
6
0
Order By: Relevance
“…It is similar to the test data adequacy of Wu et al, 38 but must be applied to specifications, not programs. Given a method, M, for creating a set of mutants, the score, S, is the number of mutants killed by the test set, k, divided by the total number of mutants, N , produced by M on r.…”
Section: A Specification Coverage Metricmentioning
confidence: 97%
See 1 more Smart Citation
“…It is similar to the test data adequacy of Wu et al, 38 but must be applied to specifications, not programs. Given a method, M, for creating a set of mutants, the score, S, is the number of mutants killed by the test set, k, divided by the total number of mutants, N , produced by M on r.…”
Section: A Specification Coverage Metricmentioning
confidence: 97%
“…If a mutant is found to be inconsistent by any of the test cases in the test set, it is considered to be killed by the test set. The ratio of killed mutants to total mutants is a coverage metric, similar to that of Wu et al, 38 but applied to specifications. The higher the ratio, the better or more completely the test set covers the specification.…”
Section: Computing a Coverage Metric With A Model Checkermentioning
confidence: 99%
“…Software fault models are injected in the code by resorting to the concept of software mutants [30]. For each injected fault, the LLVM IR code is modified to generate a mutated version able to emulate the injection of the sfm during the execution.…”
Section: Software Architecture Layermentioning
confidence: 99%
“…The number of executions needed to achieve a confidence of approximately unity in block BB j will be related to the number of theoretical mutants of BB j . Given a comprehensively defmed set of mutant productions, (for example, see [5]) the theoretical number of possible mutants could be estimated statically and specific factors which govern the mutant death rate could also be assessed such as the degrees of polyjmultinomials [1,6]; code complexity; the number of variables active in the block; the number and values of boolean variables needed to kill all mutant boolean expressions [5]; the maximum dimension of arrays, etc.…”
Section: The Execution Of a Basic Block On One Path Many Timesmentioning
confidence: 99%
“…then the logical result of the predicate would differ on at least one of the test cases. Other test data requirements can be defined for other classes of errors [2,5].…”
mentioning
confidence: 99%