Testing Java Interrupts and Timed Waits

Wildman, Luke; Long, Brad; Strooper, Paul

doi:10.1109/apsec.2004.97

Cited by 6 publications

(2 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Another area for future work is to extend the Petri-net model and the analysis to eliminate the limitations of the model discussed earlier. We have already extended the ConAn test case selection strategy and tool support to deal with interrupts and timed waits [45].…”

Section: Resultsmentioning

confidence: 99%

A method for verifying concurrent Java components based on an analysis of concurrency failures

Long

Strooper

Wildman

2006

Concurrency and Computation

View full text Add to dashboard Cite

SUMMARYThe Java programming language supports concurrency. Concurrent programs are harder to verify than their sequential counterparts due to their inherent non-determinism and a number of specific concurrency problems, such as interference and deadlock. In previous work, we have developed the ConAn testing tool for the testing of concurrent Java components. ConAn has been found to be effective at testing a large number of components, but there are certain classes of failures that are hard to detect using ConAn. Although a variety of other verification tools and techniques have been proposed for the verification of concurrent software, they each have their strengths and weaknesses. In this paper, we propose a method for verifying concurrent Java components that includes ConAn and complements it with other static and dynamic verification tools and techniques. The proposal is based on an analysis of common concurrency problems and concurrency failures in Java components. As a starting point for determining the concurrency failures in Java components, a Petri-net model of Java concurrency is used. By systematically analysing the model, we come up with a complete classification of concurrency failures. The classification and analysis are then used to determine suitable tools and techniques for detecting each of the failures. Finally, we propose to combine these tools and techniques into a method for verifying concurrent Java components. Copyright

show abstract

Section: Resultsmentioning

confidence: 99%

A method for verifying concurrent Java components based on an analysis of concurrency failures

Long

Strooper

Wildman

2006

Concurrency and Computation

View full text Add to dashboard Cite

show abstract

“…CHESS uses model checking to cover different interleavings [Prado et al 2015] for .Net parallel programs, while ConAn (Concurrency Analyzer) is utilized for unit testing of concurrent programs [Delamaro et al 2007] basing on model testing [Adhianto et al 2010] as well. ConAn was implemented for a technique to test java interrupts in another study [Wildman et al 2004]. The Automated Concurrent Testing (AutoConTest) is a method to automatically generate and run concurrent tests for a given class [Terragni and Cheung 2016].…”

Section: Related Workmentioning

confidence: 99%

A structural testing tool for MPI programs with loops

Díaz

Souza²,

Souza³

2019

Anais Do XX Simpósio Em Sistemas Computacionais De Alto Desempenho (SSCAD 2019)

View full text Add to dashboard Cite

Há uma alta demanda por programas paralelos corretos, principalmente devido às arquiteturas paralelas atuais, como clusters e processadores multi/many cores. O teste estrutural permite identificar defeitos pela cobertura de estruturas internas de programas paralelos. O não determinismo em programas paralelos traz novos desafios ao teste estrutural. Ele requer ferramentas e modelos de teste especı́ficos, capazes de cobrir primitivas de comunicação e sincronização com comportamentos dinâmicos, tais como os presentes em loops. Este artigo propõe uma nova ferramenta de software para o teste estrutural, com o objetivo de auxiliar testadores na revelação de defeitos desconhecidos associados a comunicação e presentes em estruturas de repetição de programas paralelos em C/MPI. Baseando-se na cobertura obtida, testadores podem escolher casos de teste especı́ficos e avaliar o progresso da atividade de teste. A ferramenta de teste proposta é validada com a ingestão de defeitos no código de um programa, e com a análise do suporte dado pela ferramenta para a geração de elementos requeridos e seleção de casos de teste. A ferramenta proposta automatiza parte da atividade de teste, especificamente a geração de elementos requeridos e guia a execução dos testes, reduzindo o tempo para a aplicação da atividade de teste. Nossos resultados mostram que a ferramenta de teste é capaz de revelar defeitos desconhecidos em primitivas de comunicação presentes em iterações de loops. There is a growing demand for correct parallel programs, mainly due to nowadays parallel architectures, such as clusters and multi/many-core processors. Structural testing allows the identification of defects by covering internal structures of parallel programs. Nondeterminism in parallel programs brings new challenges to the structural testing. It requires specific test model and tools, capable to cover communication and synchronization primitives with dynamic behaviors, such as those present inside of loops. This paper proposes a novel software tool for the structural testing, aiming to help testers in revealing defects associated to communication present in repetition structures of C/MPI parallel programs. Based on the obtained coverage, testers can choose specific test cases and evaluate the progress of the testing activity. We validate the proposed testing software tool by injecting a defect in a program code, and analyzing the support for generation of required elements and selection of test cases. ValiMPI tool automates part of the test activity, specifically the generation of required elements to guide test case selection, reducing the application cost of the testing activity. Our results demonstrate that the testing tool is capable to reveal unknown defects from communication in different loop iterations.

show abstract

Dealing with non-determinism in testing concurrent Java components

Wildman

Long

Strooper

2005

12th Asia-Pacific Software Engineering Conference (APSEC'05)

Self Cite

View full text Add to dashboard Cite

The testing of concurrent software components can be dificult due to the inherent non-determinism present in these components. For example, bf the same test case is run multiple times, it may produce different results. This non-determinism may lead to problems with determining eqected outputs. In this paper, we present and discuss several possible solutions to this problem in the context of testing concurrent Java components using the ConAn testing tool. We then present a recent extension to the tool that provides a general solution to this problem that is suficient to deal with the level of non-determinism that we have encountered in testing over 20 components with ConAn.

show abstract

Testing Java Interrupts and Timed Waits

Cited by 6 publications

References 11 publications

A method for verifying concurrent Java components based on an analysis of concurrency failures

A method for verifying concurrent Java components based on an analysis of concurrency failures

A structural testing tool for MPI programs with loops

Dealing with non-determinism in testing concurrent Java components

Contact Info

Product

Resources

About