2015
DOI: 10.1002/stvr.1593
|View full text |Cite
|
Sign up to set email alerts
|

Behaviour abstraction adequacy criteria for API call protocol testing

Abstract: SUMMARYCode artefacts that have non-trivial requirements with respect to the ordering in which their methods or procedures ought to be called are common and appear, for instance, in the form of API implementations and objects. Testing such code artefacts to gain confidence that they conform to their intended protocols is an important and challenging problem. This paper proposes conformance testing adequacy criteria based on covering an abstraction of the intended behavior's semantics. Thus, the criteria are in… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
10
0

Year Published

2016
2016
2021
2021

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(10 citation statements)
references
References 85 publications
0
10
0
Order By: Relevance
“…al [54] on automatic mining of EPA models, while five subjects were taken from the article by Czemerinski et. al [28]. These subjects also appear in other papers (e.g., [24,33,56,74]).…”
Section: Mutation Study On Subjects With Third Party Epasmentioning
confidence: 65%
See 2 more Smart Citations
“…al [54] on automatic mining of EPA models, while five subjects were taken from the article by Czemerinski et. al [28]. These subjects also appear in other papers (e.g., [24,33,56,74]).…”
Section: Mutation Study On Subjects With Third Party Epasmentioning
confidence: 65%
“…As previously mentioned, Czemerinski et al [28] proposed a conformance testing adequacy criteria based on covering EPA transitions. Given an EPA for a target class, the EPA transition coverage for a test suite T S is defined as follows:…”
Section: Epa Transition Coveragementioning
confidence: 99%
See 1 more Smart Citation
“…Among the papers in our set, we also found 19 studies that performed mutant analysis, which means that the researchers tried to get a better understanding about mutation faults, eg, which faults are more valuable in a particular context. A good example of this mutant analysis is the hard-mutant problem investigated by Czemerinski et al [105] where they analysed the failure rate for the hard-to-kill mutants (killed by less than 20% of test cases) using the domain partition approach.…”
Section: Attribute Framework Validationmentioning
confidence: 99%
“…which faults are more valuable in a particular context. A good example of this mutant analysis is the hard mutant problem investigated by Czemerinski et al [91] where they analysed the failure rate for the hard-to-kill mutants (killed by less than 20% of test cases) using the domain partition approach.…”
Section: Rq11 and Rq12: Which Role Does Mutation Testing Play In Eachmentioning
confidence: 99%