T HE development of Object-Oriented (OO) and component-based software is a reality. This work investigates software testing and validation in this context. Several studies related with OO testing have been carried out. In spite of being a controversial point, some researchers state that the procedural testing criteria can be easily extended to OO program testing, for instance to the testing of methods. There are few initiatives aiming at applying data-flow and mutationbased criteria, traditionally used for procedural testing, to the test of OO programs. The present work aims at contributing to identify and define resources for OO program testing and validation, considering data-flow and mutation based testing criteria, involving the unit and integration testing phases. An integrated environment for testing and validation has been developed to support the application of these criteria. This environment provides means to comparative studies amongst the criteria and to technology transfer processes. This work provides contributions to the following testing perspectives: theoretical -with the definition of testing criteria; empiricalwith the conduction of empirical studies; and to testing automation -with the specification and implementation of an integrated environment for testing and validation of OO programs. Examples are provided to illustrate the ideas and tools presented in this work. vii viii ix 1.3. ORGANIZAÇÃO DA TESE ¡¨ ¡ ¡¨ ¡ ¡¨ ¡ ¡

No abstract

Mutation testing (MT) has been found to be effective at revealing faults. However, its high cost of application, due to the high number of mutants created and the effort to determine the equivalent ones, has motivated the proposition of alternative approaches for its application. One of them, named ‘selective mutation’, aims to reduce the number of generated mutants through a reduction in the number of mutant operators. A previous relevant study resulted in the proposition of a sufficient mutant operators set for FORTRAN, indicating that it is possible to have a large cost reduction in MT application, whilst preserving a high MT score. This work investigates procedures for the determination of a sufficient mutant operators set for C programs with the perspective of contributing to the establishment of low‐cost, effective mutation‐based testing strategies. Copyright © 2001 John Wiley & Sons, Ltd.

This paper describes intra‐method control‐flow and data‐flow testing criteria for the Java bytecode language. Six testing criteria are considered for the generation of testing requirements: four control‐flow and two data‐flow based. The main reason to work at a lower level is that, even when there is no source code, structural testing requirements can still be derived and used to assess the quality of a given test set. It can be used, for instance, to perform structural testing on third‐party Java components. In addition, the bytecode can be seen as an intermediate language, so the analysis performed at this level can be mapped back to the original high‐level language that generated the bytecode. To support the application of the testing criteria, we have implemented a tool named JaBUTi (Java Bytecode Understanding and Testing). JaBUTi is used to illustrate the application of the ideas developed in this paper. Copyright © 2006 John Wiley & Sons, Ltd.

No abstract

Although software testing is a crucial activity in the software development process, only recently have more sound and consistent testing tools become available for testing Java programs and their components. These tools support mostly functional and control-flow based structural criteria. In this paper we explore control-flow and data-flow based coverage criteria to support the testing of Java programs and/or components. We also describe a testing tool, named JaBUTi, which can be used by both the component developer and the component user to test Java-based components and/or systems. To achieve this goal, the tool works at the bytecode level such that no source code is required during the testing activity. We illustrate these ideas and concepts with an example extracted from the literature.

No abstract

Agradecimentos A DEUS, pelo dom da vida e por me acompanhar em todos os momentos. Ao amigo e orientador, Prof. Dr. José Carlos Maldonado, pelo apoio, sugestões e profissionalismo na orientação deste trabalho. Aos meus familiares, em especial, aos meus pais Amauri e Leise e minhas irmãs Cibele e Andresa, pelo amor, compreensão e incentivo proporcionados. À Ellen Francine pelo amor, apoio, carinho, revisão, incentivo, esclarecimento de duvidas, etc., etc., etc., os quais foram de fundamental importância para que este trabalho pudesse ser concluído. Aos demais professores do grupo de Engenharia de Software: Prof.ª Dr.ª Rosely Sanches, Prof. Dr. Paulo Cesar Masiero e Prof.ª Dr.ª Renata P. M. Fortes. Ao meu irmão, Pe. José Carlos Frederice (Fred), pela amizade, ajuda e conselhos nas horas mais difíceis. A todos aqueles que, de alguma forma, contribuíram e colaboraram para a realização deste trabalho: Delamaro,