Control and data flow structural testing criteria for aspect-oriented programs

Lemos, Otávio Augusto Lazzarini; Vincenzi, Auri Marcelo Rizzo; Maldonado, José Carlos; Masiero, Paulo César

doi:10.1016/j.jss.2006.08.022

Cited by 52 publications

(122 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…We consider specific situations that happens in OO and AO to be represented in the models and then generate relevant test requirements for testing dynamic behaviour of that program. We use the Java bytecode to generate the underlying model for programs written in Java and AspectJ [11,14,16,24,46]. We take advantage of the AspectJ weaving process to extract static information of two different programming languages from one unified representation (the Java bytecode).…”

Section: Creating An Underlying Modelmentioning

confidence: 99%

“…In our research [11], we developed an approach for unit testing of AO programs considering a method or an advice as the unit under testing. We proposed a model to represent the control flow of a unit and the join points that may activate an advice.…”

Section: Structural Requirements For Ao Programsmentioning

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: Creating An Underlying Modelmentioning

confidence: 99%

Section: Structural Requirements For Ao Programsmentioning

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

“…Since aspect-oriented programming introduces new constructs and programming means for separation of concerns, testing of AO programs is more sophisticated and challenging in which the existing techniques for testing cannot accommodate this matter and need to be leveraged or extended. Furthermore, research in AO testing has focused on approaches such as code-based structural testing [6,7], specification-based functional testing [8][9][10], use of random testing [11], and mutation testing [12]. Surveys by [13] and [14] have examined the effectiveness of testing techniques for AO programs which include data flow based unit testing, state-based approach, aspect flow graph based technique, unit testing aspectual behaviour, and model-based approach.…”

Section: Introductionmentioning

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

“…Em Spoto et al (2000)é proposta uma técnica para identificar definição e utilização de variáveis persistentes em aplicações de banco de dados relacional e foi definido um conjunto de critérios estruturais de teste de unidade e de integração. Em Lemos et al (2007) são definidos critérios estruturais para lidar com características específicas de programas orientados a aspecto. Delamaro et al (2007b) discutem como usar as características da análise de bytecode Java e como estendê-la para a implementação de critérios de teste estruturais para dois domínios específicos: programas orientados a aspectos e aplicações de banco de dados.…”

Section: Lista De Abreviaturas E Siglasunclassified

Critérios de teste baseados em grafo de cena para aplicações de realidade virtual

Bezerra¹

View full text Add to dashboard Cite

Control and data flow structural testing criteria for aspect-oriented programs

Cited by 52 publications

References 16 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

Critérios de teste baseados em grafo de cena para aplicações de realidade virtual

Contact Info

Product

Resources

About