Test criteria and coverage measures for software integration testing

Spillner, Andreas

doi:10.1007/bf00402648

Cited by 17 publications

(4 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The coverage most often encompasses control flow (such as statement coverage or branch coverage) but can also relate to the data flow (such as all definitions). This translates badly to integration tests as it then still relies on which statements in the integrated components are executed, just with a relation to the interface of the components [25].…”

Section: Assessing the Quality Of Slt Programsmentioning

confidence: 99%

Exploring the Mysteries of System-Level Test

Polian,

Anders,

Becker

et al. 2021

Preprint

View full text Add to dashboard Cite

System-level test, or SLT, is an increasingly important process step in today's integrated circuit testing flows. Broadly speaking, SLT aims at executing functional workloads in operational modes. In this paper, we consolidate available knowledge about what SLT is precisely and why it is used despite its considerable costs and complexities. We discuss the types or failures covered by SLT, and outline approaches to quality assessment, test generation and root-cause diagnosis in the context of SLT. Observing that the theoretical understanding for all these questions has not yet reached the level of maturity of the more conventional structural and functional test methods, we outline new and promising directions for methodical developments leveraging on recent findings from software engineering.

show abstract

Section: Assessing the Quality Of Slt Programsmentioning

confidence: 99%

Exploring the Mysteries of System-Level Test

Polian,

Anders,

Becker

et al. 2021

Preprint

View full text Add to dashboard Cite

show abstract

“…Though the concept of coverage was originally proposed for unit testing on the code level, it has been extended to different contexts. Spillner [12] has proposed some coverage criteria for integration testing. In the context of control-flow based integration testing, the interactions among modules and operations were considered.…”

Section: Test Selection: Related Workmentioning

confidence: 99%

Efficient Testing based on Logical Architecture

Liu

Spichkova

Schmidt

et al. 2015

Proceedings of the ASWEC 2015 24th Australasian Software Engineering Conference

View full text Add to dashboard Cite

The rapid increase of software-intensive systems' size and complexity makes it infeasible to exhaustively run testing on the low level of source code. Instead, the testing should be executed on the high level of system architecture, i.e., at a level where component or subsystems relate and interoperate or interact collectively with the system environment. Testing at this level is system testing, including hardware and software in union. Moreover, when integrating complex, distributed systems and providing support for conformance, interoperability and interoperation tests, we need to have an explicit test description. In this vision paper, we discuss (1) how to select tests from logical architecture, especially based on the dependencies within the system, and (2) how to represent the selected tests in explicit and readable manner, so that the software systems can be cost-efficiently maintained and evolved over their entire life-cycle. In addition, we further study the relevance between different tests, based on which, we can optimise the test suites for efficient testing, and propose optimal resource allocation strategies for cloud-based testing.

show abstract

“…Agents have run time response and adaptability. Coverage criteria for testing can be applied to both code and model [ 21 ]. Code base conform that all code are covered in term of statements, and so forth while model based coverage requires the different interaction from different states of the system, represented in specific model [ 22 ].…”

Section: Related Workmentioning

confidence: 99%

An Approach to Model Based Testing of Multiagent Systems

Rehman

Nadeem

2015

The Scientific World Journal

View full text Add to dashboard Cite

Autonomous agents perform on behalf of the user to achieve defined goals or objectives. They are situated in dynamic environment and are able to operate autonomously to achieve their goals. In a multiagent system, agents cooperate with each other to achieve a common goal. Testing of multiagent systems is a challenging task due to the autonomous and proactive behavior of agents. However, testing is required to build confidence into the working of a multiagent system. Prometheus methodology is a commonly used approach to design multiagents systems. Systematic and thorough testing of each interaction is necessary. This paper proposes a novel approach to testing of multiagent systems based on Prometheus design artifacts. In the proposed approach, different interactions between the agent and actors are considered to test the multiagent system. These interactions include percepts and actions along with messages between the agents which can be modeled in a protocol diagram. The protocol diagram is converted into a protocol graph, on which different coverage criteria are applied to generate test paths that cover interactions between the agents. A prototype tool has been developed to generate test paths from protocol graph according to the specified coverage criterion.

show abstract

Test criteria and coverage measures for software integration testing

Cited by 17 publications

References 9 publications

Exploring the Mysteries of System-Level Test

Exploring the Mysteries of System-Level Test

Efficient Testing based on Logical Architecture

An Approach to Model Based Testing of Multiagent Systems

Contact Info

Product

Resources

About