Automating the mutation testing of aspect-oriented Java programs

Ferrari, Fabiano Cutigi; Nakagawa, Elisa Yumi; Rashid, Awais; Maldonado, José Carlos

doi:10.1145/1808266.1808274

Cited by 29 publications

(11 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…They argue that reducing the amount of equivalent mutants generated by some operators would consequently reduce the cost of mutation testing as a whole. The authors used three testing tools (namely, AjMutator [20], Proteum/AJ [21] and MuJava [60]) to assess their technique. Apart from traditional class-level mutation operators [59], Wedyan and Ghosh applied a subset of operators defined in our previous work [12] using the Proteum/AJ and AjMutator tools.…”

Section: Related Work On Mutation-based Testingmentioning

confidence: 99%

“…7 http://www.eclipse.org/ajdt/-accessed in 23/07/2015. 8 The testing process and criterion application was supported by the Proteum/AJ tool [21]. More details can be found in a previous paper [26].…”

Section: Endnotesmentioning

confidence: 99%

“…Ever since, the software testing community has been investigating ways of dealing with the challenges described by them. In summary, research on testing of AO programs (hereafter called AO testing) has been mainly concerned with: (i) the characterisation of fault types and bug patterns [2][3][4][5][6][7], (ii) the definition of underlying test models and test selection criteria [8][9][10][11][12][13][14][15][16][17][18] and (iii) the provision of automated tool support [11,14,16,[18][19][20][21][22]. In particular, structural-based and mutation-based testing have been on focus by several research initiatives [8,9,[11][12][13][14][15][16][17][18][19][20][21][22][23][24][25][26][27][28][29].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Testing of aspect-oriented programs: difficulties and lessons learned based on theoretical and practical experience

et al. 2015

View full text Add to dashboard Cite

Background: Since the first discussions of new challenges posed by aspect-oriented programming (AOP) to software testing, the real difficulties of testing aspect-oriented (AO) programs have not been properly analysed. Firstly, despite the customisation of traditional testing techniques to the AOP context, the literature lacks discussions on how hard it is to apply them to (even ordinary) AO programs based on practical experience. Secondly, and equally important, due to the cautious AOP adoption focused on concern refactoring, test reuse is another relevant issue that has been overlooked so far. This paper deals with these two issues. It discusses the difficulties of testing AO programs from three perspectives: (i) structural-based testing, (ii) fault-based testing and (iii) test set reuse across paradigms. Methods: Perspectives (i) and (ii) are addressed by means of a retrospective of research done by the authors' group. We analyse the impact of using AOP mechanisms on the testability of programs in terms of the underlying test models, the derived test requirements and the coverage of such requirements. The discussion is based on our experience on developing and applying testing approaches and tools to AspectJ programs at both unit and integration levels. Perspective (iii), on the other hand, consists of recent exploratory studies that analyse the effort to adapt test sets for refactored systems and the quality of such test sets in terms of structural coverage. Results: Building test models for AO programs imposes higher complexity when compared to the OO paradigm. Besides this, adapting test suites for OO programs to AO equivalent programs tends to require less effort than doing the other way around, and resulting suites achieve similar quality levels for small-sized aplications. Conclusions: The conclusion is that building test models for AO programs, as well as deriving and covering paradigm-specific test requirements, is not straightforward as it has been for procedural and object-oriented (OO) programs at some extent. Once you have test suites in conformance with programs implemented in both paradigms, the quality of such suited in termos of code coverage may vary depending on the size and characteristics of the applications under testing.

show abstract

Section: Related Work On Mutation-based Testingmentioning

confidence: 99%

Section: Endnotesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Testing of aspect-oriented programs: difficulties and lessons learned based on theoretical and practical experience

et al. 2015

View full text Add to dashboard Cite

show abstract

“…The tool detects equivalent mutants by leveraging on the static analysis of the compiler. Other tools that were proposed to automate generation of mutants for AspectJ programs are MuAspectJ [50] and Proteum/AJ [51].…”

Section: Mutation Testing For Aspect-oriented Programsmentioning

confidence: 99%

Towards Semantic Mutation Testing of Aspect-Oriented Programs

Ghani¹

2013

JSEA

View full text Add to dashboard Cite

Aspect-oriented programs have received much attention from software testing researchers. Various testing techniques and approaches have been proposed to tackle issues and challenges when testing aspect-oriented programs including traditional mutation testing. In traditional mutation testing of aspect-oriented programs, mutants are generated by making small changes to the syntax of the aspect-oriented language. Recently, a new approach known as semantic mutation testing has been proposed. This approach mutates the semantics of the language in which the program is written. The mutants generated misunderstandings of the language which are different classes of faults. Aspect-oriented programming presents itself with different properties that can be further explored with respect to semantic mutation testing. This paper describes various possible scenarios that semantic mutation testing strategy might have particular value in testing aspect-oriented programs.

show abstract

“…For instance, Proteum/AJ was developed using knowledge contained in RefTEST; i.e., it was developed through specialization of the RefTEST for the mutation testing of aspect-oriented programs, specifically written in AspectJ 13 [18], [19]. Proteum/AJ automates a set of AO-specific mutation operators [17] and supports the basic steps of mutation testing [13], such as mutant handling, test case handling, and mutant analysis.…”

Section: B Using Reftestmentioning

confidence: 99%

Towards the Open Source Reference Architectures

Nakagawa

Maldonado

2011

2011 Fifth Brazilian Symposium on Software Components, Architectures and Reuse

Self Cite

View full text Add to dashboard Cite

Software architectures have received increasing attention by playing a significant role in determining the success and quality of software systems. In particular, reference architecture is a special type of architecture that captures the essence of software systems of a specific domain, achieving therefore well-recognized understanding of that domain. In spite of this, it is not observed concern in order to widely disseminate reference architectures and, as a consequence, the knowledge encompassed by these architectures. At the same time, Open Source Software (OSS) has been largely developed and used in both academy and industry. A diversity of OSS has been made available and has contributed to the software development through dissemination of knowledge that is encompassed mainly in the source code. Specifically, its success is due to OSS licences that have adequately supported its development and evolution. Thus, applying this same idea in order to disseminate reference architectures seems to be very interesting. The main contribution of this paper is to propose Open Source Reference Architecture (OSRA) that, based on principles of OSS, aims at promoting dissemination and evolution of reference architectures, intending to contribute to a more effective software development.

show abstract

Automating the mutation testing of aspect-oriented Java programs

Cited by 29 publications

References 15 publications

Testing of aspect-oriented programs: difficulties and lessons learned based on theoretical and practical experience

Testing of aspect-oriented programs: difficulties and lessons learned based on theoretical and practical experience

Towards Semantic Mutation Testing of Aspect-Oriented Programs

Towards the Open Source Reference Architectures

Contact Info

Product

Resources

About