2006
DOI: 10.1002/spe.726
|View full text |Cite
|
Sign up to set email alerts
|

Establishing structural testing criteria for Java bytecode

Abstract: 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. … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
38
0
28

Year Published

2008
2008
2024
2024

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 29 publications
(66 citation statements)
references
References 20 publications
0
38
0
28
Order By: Relevance
“…Notice that nodes 2-6 have edges to nodes 8, 9, and 11; we use only one edge from the try box for improving the legibility of the graph. The exception handling notation we use is adapted from the notations proposed by Sinha and Harrold [13] and Vincenzi et al [14].…”
Section: ¦ ¥mentioning
confidence: 99%
See 1 more Smart Citation
“…Notice that nodes 2-6 have edges to nodes 8, 9, and 11; we use only one edge from the try box for improving the legibility of the graph. The exception handling notation we use is adapted from the notations proposed by Sinha and Harrold [13] and Vincenzi et al [14].…”
Section: ¦ ¥mentioning
confidence: 99%
“…For instance, a block that declares a NullPointerException will be executed only when such an exception is thrown. However, in general, there are no constraint indicating in which condition such an exception will be thrown.We classify paths that depend on an exception being thrown as exception-dependent paths (EDPs) [7], as oppose to exception-free paths (EFPs) [14]. According to an analysis performed over a sample of 100 open source projects called SF100 [8] 1 , we discovered that almost one third of the methods have at least one EDP [7].…”
mentioning
confidence: 99%
“…Inspired by Harrold and Rothermel's criteria, Vincenzi et al [49] presented a set of testing criteria based on both control flow and data flow for unit (i.e. method) testing.…”
Section: Structural Requirements For Procedural and Oo Programsmentioning
confidence: 99%
“…Outros autores partiram do princípio de que o código fonte dos componentes está disponível e propuseram o uso de téc-nicas de teste baseadas em implementação, como o trabalho de Harrold e Rothermel (1994), por exemplo. Por outro lado, mesmo considerando o encapsulamento dos componentes, Vincenzi et al (2003) propuseram o uso da ferramente JaBUTi (Vincenzi et al, 2006) para realizar o teste estrutural de componentes escritos em Java, uma vez que a ferramenta pode usar o bytecode do componente para gerar os requisitos de teste e avaliar a cobertura estrutural. Tabela 2.1: Abordagens de teste orientado a objetos aplicadas a componentes.…”
Section: Abordagens De Teste De Componentesunclassified
“…Para viabilizar essa estratégia foi proposta a ferramenta FATEsC (Ferramenta de Apoio ao Teste Estrutural de Componentes) (Teixeira et al, 2007b), que é uma extensão da ferramenta JaBUTi (Vincenzi et al, 2006).…”
Section: Metadadosunclassified