2011Unpublished venueRequires access

Integration testing object-oriented software systems: An experiment-driven research approach

Yvan Labiche

Open publisher page 7 citations

Abstract

Any incremental class testing approach has to answer the two following questions: What integration process, indicating in which order classes are (integration) tested, should be selected? Which test design techniques should be applied to unit and integration test classes? Although there is a fairly large number of reported works on both questions, much remains to be done. On the one hand, class unit/integration testing techniques have mostly been described without any consideration for any integration process. On the other hand, integration processes have been suggested without much consideration for how they could be used in practice, along with class unit/integration testing techniques. There is a lack of research and practical results on how a class integration process can be used to conduct class unit/integration testing. This paper summarizes the problem and suggests an experiment-driven research approach to solve it.

About this research paper

What this paper is about

Any incremental class testing approach has to answer the two following questions: What integration process, indicating in which order classes are (integration) tested, should be selected? Which test design techniques should be applied to unit and integration test classes? Although there is a fairly large number of reported works on both questions, much remains to be done. On the one hand, class unit/integration testing techniques have mostly been described without any consideration for any integration process. On the other hand, integration processes have been suggested without much consideration for how they could be used in practice, along with class unit/integration testing techniques. There is a lack of research and practical results on how a class integration process can be used to conduct class unit/integration testing. This paper summarizes the problem and suggests an experiment-driven research approach to solve it.

Why it matters

OpenAlex reports 7 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Any incremental class testing approach has to answer the two following questions: What integration process, indicating in which order classes are (integration) tested, should be selected? Which test design techniques should be applied to unit and integration test classes? Although there is a fairly large number of reported works on both questions, much remains to be done. On the one hand, class unit/integration testing techniques have mostly been described without any consideration for any integration process. On the other hand, integration processes have been suggested without much consideration for how they could be used in practice, along with class unit/integration testing techniques. There is a lack of research and practical results on how a class integration process can be used to conduct class unit/integration testing. This paper summarizes the problem and suggests an experiment-driven research approach to solve it.

Key concepts: Integration testing, Unit testing, Computer science, Class (philosophy), Process (computing), White-box testing, System integration, Software engineering

Related papers

Back to paper searchBrowse research topicsOriginal source
Integration testing object-oriented software systems: An experiment-driven research approach — Research Paper | ScholarLens