Component-based integration testing from UML interaction diagrams

Machado, Patrícia D. L.; Figueiredo, Jorge C. A. de; Lima, Emerson F. A.; Barbosa, Ana Esther Victor; Lima, Helton Souza

doi:10.1109/icsmc.2007.4414070

Cited by 9 publications

(6 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Those properties could be modeled in the Quality of Service constraint language (QoSCL) [23]. For gathering data to improve the testing process monitoring has already been used by some approaches [34,38,39,43,53], but also the use of other measures like fault tree analysis [76] or usage profiling [57] seem very promising. We think that model refinement is the most promising assessment type, as in the end all can be represented in a modeling language, which enables all of the advantages, like easy communication between stakeholder or (semi)automation.…”

Section: Implications For Future Researchmentioning

confidence: 99%

“…Summing up we can say that [2,3,8,11,33,35,36,50,56,62,68,77,78,88,93,95,97] use coverage criteria for the appropriate domain, [38,39,43] use metrics, [34,53] do monitoring of the testing progress, [57,63,74,81] combine different models or other data like usage profiles for doing the assessment of the test process, and [24,73] provide useful information, i.e. suggestions for the best integration order strategy for the tester.…”

Section: Assessment Type (Rq2)mentioning

confidence: 99%

“…In their approach Machado et al [57] test cases are selected based on the probability distribution, according to usage profiles and criticality analysis. As of Matiello et al [63] do the prioritization of test cases by combining operational profiles for services, timed input and output automata and UML sequence diagrams.…”

Section: Assessment Type (Rq2)mentioning

confidence: 99%

See 2 more Smart Citations

Software paradigms, assessment types and non-functional requirements in model-based integration testing

Häser

Felderer

Breu

2014

Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering

View full text Add to dashboard Cite

Context:In modern systems, like cyber-physical systems, where software and physical services are interacting, safety, security or performance play an important role. In order to guarantee the correct interoperability of such systems, with respect to functional and non-functional requirements, integration testing is an effective measure to achieve this. Model-based testing moreover not only enables early definition and validation, but also test automation. This makes it a good choice to overcome urgent challenges of integration testing. Objective: Many publications on model-based integration testing (MBIT) approaches can be found. Nevertheless, a study giving a systematic overview on the underlying software paradigms, measures for guiding the integration testing process as well as non-functional requirements they are suitable for, is missing. The aim of this paper is to find and synthesize the relevant primary studies to gain a comprehensive understanding of the current state of model-based integration testing. Method: For synthesizing the relevant studies, we conducted a systematic literature review (SLR) according to the guidelines of Kitchenham. Results: The systematic search and selection retrieved 83 relevant studies from which data has been extracted. Our review identified three assessment criteria for guiding the testing process, namely static metrics, dynamic metrics and stochastic &random. In addition it shows that just a small fraction considers non-functional requirements. Most approaches are for component-oriented systems. Conclusion: Results from the SLR show that there are two major research gaps. First, there is an accumulated need for approaches in the MBIT field that support non-functional requirements, as they are gaining importance. Second, means for steering the integration testing process, especially together with automation, need to evolve.

show abstract

Section: Implications For Future Researchmentioning

confidence: 99%

Section: Assessment Type (Rq2)mentioning

confidence: 99%

See 1 more Smart Citation

Software paradigms, assessment types and non-functional requirements in model-based integration testing

Häser

Felderer

Breu

2014

Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering

View full text Add to dashboard Cite

show abstract

“…Machado et al [18] present a UML based approach for integration-level testing using Object Constraint Language (OCL) [19]. The authors illustrate a complete test process for integration testing.…”

Section: Related Workmentioning

confidence: 99%

Identification and Selection of Interaction Test Scenarios for Integration Testing

Mussa

Khendek

2013

System Analysis and Modeling: Theory and Practice

View full text Add to dashboard Cite

Abstract. Integration testing checks for compatibility and interoperability between the components in the system. Integration test models are, typically, generated independently from the other testing level models. In our research, we aim at a model-based framework across unit, integration, and acceptance level testing. This paper contributes to this framework and for the generation of integration test models from unit test models. More precisely, we focus on component interaction test scenarios identification and selection. Following our approach, at each integration step, unit test cases with interaction scenarios involving the component and the context are identified, selected and merged to build the integration test model for the next step. Unit test stubs and drivers are reused in the integration test model. Redundant test cases are eliminated from the generated test models.

show abstract

“…It verifies the information between the component producer and the user. Machado et al [21] presented a UMLbased approach to integration testing using UML diagrams including the Object Constraint Language. Zheng and Bundel [31] [23].…”

Section: Related Workmentioning

confidence: 99%

A model-based testing technique for component-based real-time embedded systems

Guan

Offutt

2015

2015 IEEE Eighth International Conference on Software Testing, Verification and Validation Workshops (ICSTW)

View full text Add to dashboard Cite

The growing complexity of modern real-time embedded systems is leading to increased use of component-based software engineering (CBSE) technology. Although many ideas have been proposed for building component-based real-time embedded software, techniques for testing component-based realtime systems are scarce. The challenges not only come from the integration of different types of components through their interfaces but also include the composition of extra-functional properties. In an embedded system, extra-functional requirements are as important as functional requirements. A real-time embedded system needs to achieve its functionality under the constraints caused by its extra-functional properties. Correct functional behavior with regard to timing properties is essential to real-time embedded system. This paper focuses on real-time requirements instead of all extra-functional requirements. Therefore, they should be considered while testing embedded software behavior. This paper addresses problems that emerge during the integration of component-based real-time embedded software. It presents a test model that depicts both inter-component and intra-component relationships in component-based real-time embedded software and identifies key test elements. The test model is realized using a family of graph-based test models in which that describe functional interactions and their dependence relationships, as well as the time-dependent interaction among components. By using a graph-based test model, this paper presents a novel family of test adequacy criteria that help generate effective test cases and new algorithms to facilitate automate generation of the test cases.

show abstract

Component-based integration testing from UML interaction diagrams

Cited by 9 publications

References 6 publications

Software paradigms, assessment types and non-functional requirements in model-based integration testing

Software paradigms, assessment types and non-functional requirements in model-based integration testing

Identification and Selection of Interaction Test Scenarios for Integration Testing

A model-based testing technique for component-based real-time embedded systems

Contact Info

Product

Resources

About