Toward the determination of sufficient mutant operators for C

Software Testing Verification and Reliability

Volumn 11, Issue 2, 2001, Pages 113-136

  Barbosa, Ellen Francine ^a   Maldonado, José Carlos ^a   Vincenzi, Auri Marcelo Rizzo ^a  

^a UNIVERSITY OF SÃO PAULO   (Brazil)

Author keywords

Mutation testing; Software testing; Sufficient mutant operators

Indexed keywords

C (PROGRAMMING LANGUAGE); COMPUTER SOFTWARE SELECTION AND EVALUATION; FAILURE ANALYSIS; RELIABILITY;

MUTANT OPERATORS; MUTATION TESTING; SOFTWARE TESTING;

SOFTWARE ENGINEERING;

EID: 0035361086     PISSN: 09600833     EISSN: None     Source Type: Journal    
DOI: 10.1002/stvr.226     Document Type: Article

References (22)

1. Hints on test data selection: Help for the practicing programmer
2. Theoretical and empirical studies on using program mutation to test the functional correctness of programs
3. An experimental evaluation of selective mutation
4. An empirical comparison of data flow and mutation-based test adequacy criteria
5. Mutation versus all-uses: An empirical evaluation of cost, strength, and effectiveness
6. Reducing the cost of mutation testing: An empirical study
7. An experimental determination of sufficient mutant operators
8. A comparison of selective mutation in C and FORTRAN
9. Mutation analysis
10. Performance, effectiveness, and reliability issues in software testing
11. A contribution for the determination of a sufficient mutant operators set for C-program testing
12. Interface mutation: An approach for integration testing
13. An extended overview of the Mothra software testing environment
14. Proteum: A tool for the assessment of test adequacy for C programs
15. Design of mutant operators for the C programming language
16. The cost of data flow testing: An empirical study
17. Reducing the cost of regression testing by using selective mutation
18. Selecting software test data using data flow information
19. Comparison of program testing strategies
20. Efficiency of mutation operators and selective mutation strategies: An empirical study
21. Interface mutation: Assessing testing quality at interprocedural level
22. Unit and integration testing strategies for C programs using mutation-based criteria