A method for the automatic generation of test suites from object models

Cavarra, Alessandra; Davies, Jim

doi:10.1145/952742.952748

Cited by 4 publications

(9 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Many of the related works reported in the literature attempt to use UML state chart diagrams for testing [3,15,16,19]. State chart diagrams are appropriate in the context of class level testing as these do not represent message and activity sequences and communications.…”

Section: Comparison With Related Workmentioning

confidence: 99%

“…Further, we use exactly the same UML diagrams developed for analysis and design, without requiring any additional formalism or effort specifically made for testing purposes. Many reported methods require augmenting the UML specifications with specific annotations to facilitate the test derivation, or an additional formalism that the methods can process [19,20,21].…”

Section: Comparison With Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Test Case Generation from Behavioral UML Models

Swain¹,

Mohapatra²

2010

IJCA

View full text Add to dashboard Cite

We propose an integrated approach to generate test cases from UML sequence and activity diagrams. We first transform these UML diagrams into a graph. Then, we propose an algorithm to generate test scenarios from the constructed graph. Next, the necessary information for test case generation, such as method-activity sequence, associated objects, and constraint conditions are extracted from test scenario. Our approach reduces the number of test cases and still achieves adequate test coverage. We achieve message-activity path coverage and category partitioning method for each predicate conditions found in the specific path of the design model.

show abstract

Section: Comparison With Related Workmentioning

confidence: 99%

Section: Comparison With Related Workmentioning

confidence: 99%

Test Case Generation from Behavioral UML Models

Swain¹,

Mohapatra²

2010

IJCA

View full text Add to dashboard Cite

show abstract

“…In fact, when left unspecified, sequence diagrams are by default regulated by a weak partial order and therefore we can consider the whole diagram within a seq 3 combined fragment (see definition of the seq operator in section 2).…”

Section: The Function Frag: Instance × Location → Combined-fragment Rmentioning

confidence: 99%

“…The additional expressive power of this extension also has advantages for automatic test generation: we can specify scenarios we want the system to necessarily exhibit or avoid, and so on. Future work includes the extension of our language for test directives in [3] w.r.t. the extended sequence diagrams.…”

Section: Conclusion and Related Workmentioning

confidence: 99%

Formalizing Liveness-Enriched Sequence Diagrams Using ASMs

Cavarra

Küster-Filipe

2004

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. In UML 2.0 sequence diagrams have been considerably extended, influenced by Live Sequence Charts (LSCs), a very expressive extension of Message Sequence Charts (MSC) with liveness. Nonetheless, fundamental liveness properties can still not be expressed in the new sequence diagrams. In recent work, we have proposed to solve this by enriching sequence diagrams with a simple but powerful Object Constraint Language (OCL) template for liveness. In this paper, we show how to formalize our liveness-enriched sequence diagrams using Abstract State Machines. Sequence diagrams still have several open problems. For example, the semantics of some of the newly introduced operators is ambiguous, and it is not clear how they can be used or combined with other operators. We address some of these issues in the paper. Finally, a further advantage of using ASMs as a semantic model concerns synthesis. It is our ultimate goal to be able to synthesise automatically a state-based object system from our richer sequence diagrams. ASMs are a state-based and operational formalism which therefore eases this task considerably.

show abstract

“…They are used for validating software models [108][109][110] and implementation verification [111][112][113][114][115][116][117].…”

Section: Model-based Testingmentioning

confidence: 99%

A Model-Driven Framework for Context-Dependent Component Testing

Javed¹

View full text Add to dashboard Cite

A model-driven framework for context-dependent testing of components (MD-CDCT) is the outcome of this research. Component-based Software Development (CSD) is a process in which software applications are developed by reusing existing components. Primarily, this research devises a technique for evaluating and extending the test adequacy of a component for its reuse in a new context (system). Secondly, it uses the Model-Driven Architecture (MDA) in the context of component testing and CSD. MDA is an emerging approach for developing software applications from high-level models. In MDA, models at various levels of abstraction are used to automate software development and testing activities.When a general-purpose component is used in a new context, it needs to be thoroughly tested for that context. MD-CDCT models the usage of a component, in a context of interest, using usage scenarios and interaction diagrams. From these scenarios, test cases for performing CDCT are automatically generated using a model-driven tool. We then evaluate and extend the adequacy of the generated test cases by comparing them with the test cases that were executed during This approach is novel in that it applies the emerging MDA technology to contextdependent testing of components. The proposed framework benefits from the advantages of an MDA-based approach, such as portability, interoperability and maintainability. Another novelty is the use of test cases, which are executed during component testing, to evaluate and extend the adequacy of component testing. We have developed two prototype tools (a tool for test case execution, and a tool for test suite comparison) to provide tool support for this approach.Five case studies are used to illustrate and evaluate the MD-CDCT. The first is a simulation of a Vending Machine system. This case study illustrates the application of MD-CDCT. The second is a simulation of an ATM system. This case study shows how to generate test cases from software models by making use of the model transformation technology. The third and fourth case studies show how the comparison of test suites can be used to evaluate and extend their test adequacy. The final case study evaluates the framework and the prototype tool support on a non-trivial system, which is Lucene (a search engine).iii

show abstract

A method for the automatic generation of test suites from object models

Cited by 4 publications

References 0 publications

Test Case Generation from Behavioral UML Models

Test Case Generation from Behavioral UML Models

Formalizing Liveness-Enriched Sequence Diagrams Using ASMs

A Model-Driven Framework for Context-Dependent Component Testing

Contact Info

Product

Resources

About