A survey of coverage based testing tools

Yang, Qian; Li, J. Jenny; Weiss, David M.

doi:10.1145/1138929.1138949

Cited by 77 publications

(55 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…There might be classes where no mutants are selected at all, and yet the effectiveness of the sampled set would not be affected at project level. This is contrary to common practice, where test suite quality metrics are often calculated per class [29]. In that sense, studies based on the metric effectiveness lack of an analysis of the representativeness of the sampled set of mutants; namely, how using a sampled set of mutants influences the mutation coverage calculated for each class.…”

Section: Introductionmentioning

confidence: 89%

Evaluating random mutant selection at class-level in projects with non-adequate test suites

Parsai

Murgia

Demeyer

2016

Proceedings of the 20th International Conference on Evaluation and Assessment in Software Engineering

View full text Add to dashboard Cite

Mutation testing is a standard technique to evaluate the quality of a test suite. Due to its computationally intensive nature, many approaches have been proposed to make this technique feasible in real case scenarios. Among these approaches, uniform random mutant selection has been demonstrated to be simple and promising. However, works on this area analyze mutant samples at project level mainly on projects with adequate test suites. In this paper, we fill this lack of empirical validation by analyzing random mutant selection at class level on projects with non-adequate test suites. First, we show that uniform random mutant selection underachieves the expected results. Then, we propose a new approach named weighted random mutant selection which generates more representative mutant samples. Finally, we show that representative mutant samples are larger for projects with high test adequacy.

show abstract

Section: Introductionmentioning

confidence: 89%

Evaluating random mutant selection at class-level in projects with non-adequate test suites

Parsai

Murgia

Demeyer

2016

Proceedings of the 20th International Conference on Evaluation and Assessment in Software Engineering

View full text Add to dashboard Cite

show abstract

“…There is a plenty of work in the literature on testing coverage criteria [43]. Those that are widely referred to include the control flow coverage criteria [21], dataflow coverage criteria [22], logic coverage criteria [44], interface coverage criteria [24], and mutation score [36].…”

Section: Related Workmentioning

confidence: 99%

Basis Path Coverage Criteria for Smart Contract Application Testing

Wang

Xie

et al. 2019

2019 International Conference on Cyber-Enabled Distributed Computing and Knowledge Discovery (CyberC)

View full text Add to dashboard Cite

The widespread recognition of the smart contracts has established their importance in the landscape of next generation blockchain technology. However, writing a correct smart contract is notoriously difficult. Moreover, once a state-changing transaction is confirmed by the network, the result is immutable. For this reason, it is crucial to perform a thorough testing of a smart contract application before its deployment. This paper's focus is on the test coverage criteria for smart contracts, which are objective rules that measure test quality. We analyze the unique characteristics of the Ethereum smart contract program model as compared to the conventional program model. To capture essential control flow behaviors of smart contracts, we propose the notions of whole transaction basis path set and bounded transaction interaction. The former is a limited set of linearly independent inter-procedural paths from which the potentially infinite paths of Ethereum transactions can be constructed by linear combination, while the latter is the permutations of transactions within a certain bound. Based on these two notions, we define a family of path-based test coverage criteria. Algorithms are given to the generation of coverage requirements. A case study is conducted to compare the effectiveness of the proposed test coverage criteria with random testing and statement coverage testing.

show abstract

“…Tools can help to measure how thoroughly software is tested. A number of tools to measure coverage criteria exist; some of them have unique features tailored to a certain application domain [32].…”

Section: Test Approachesmentioning

confidence: 99%

Integrated Test Development

Bijlsma

Passier

Pootjes

et al. 2018

Proceedings of the 7th Computer Science Education Research Conference

View full text Add to dashboard Cite

Creating test cases is a difficult task for students. The number of existing recommendations on how to create test cases is overwhelming. There is a lack of guidelines on how to apply those recommendations one step after another. This problem even becomes more complicated when students are taught to refactor their code as a habit. We propose an approach to teach students how to develop and test their code systematically, with refactoring integrated. In our approach, we pay attention to both functionality and robustness. CCS CONCEPTS• Software and its engineering → Software design engineering; Software development techniques;

show abstract

A survey of coverage based testing tools

Cited by 77 publications

References 4 publications

Evaluating random mutant selection at class-level in projects with non-adequate test suites

Evaluating random mutant selection at class-level in projects with non-adequate test suites

Basis Path Coverage Criteria for Smart Contract Application Testing

Integrated Test Development

Contact Info

Product

Resources

About