Using AOP for Discovering and Defining Executable Test Cases

Kumar, Philipp; Baar, Thomas

doi:10.1007/978-3-642-11486-1_23

Cited by 2 publications

(4 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For problem 1, our approach performs dynamic analysis of the original system: we execute each test method and determine whether it exercises any functionality to be reused. For problem 2, we use a variation on the notion of ‘capture‐and‐replay’ of execution traces : roughly speaking, we determine which objects are passed from a non‐reused method to a reused method and the results that are returned, we record a subset of this information, and we check that this subset is consistent with the behaviour in the target system when the reused functionality is transplanted there.…”

Section: Our Approachmentioning

confidence: 99%

“…A variety of work has considered the automated generation of unit tests from system test traces (i.e., the sequence of methods called, and changes to the state of objects manipulated, during an actual execution of system tests), largely for the purpose of regression testing . The central idea of all these is that the portion of a system test trace that deals with a given unit is to be extracted from the overall trace; this subtrace can then be compared against future executions of the unit, where differences indicate behavioural changes, and thus likely errors.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Validating pragmatic reuse tasks by leveraging existing test suites

Makady

Walker

2012

Softw Pract Exp

View full text Add to dashboard Cite

SUMMARYTraditional industrial practice often involves the ad hoc reuse of source code that was not designed for that reuse. Such pragmatic reuse tasks play an important role in disciplined software development. Pragmatic reuse has been seen as problematic due to a lack of systematic support, and an inability to validate that the reused code continues to operate correctly within the target system. Although recent work has successfully systematized support for pragmatic reuse tasks, the issue of validation remains unaddressed. In this paper, we present a novel approach and tool to semi‐automatically reuse and transform relevant portions of the test suite associated with pragmatically reused code, as a means to validate that the relevant constraints from the originating system continue to hold, while minimizing the burden on the developer. We conduct a formal experiment with experienced developers, to compare the application of our approach versus the use of a standard IDE (the ‘manual approach’). We find that, relative to the manual approach, our approach: reduces task completion time; improves instruction coverage by the reused test cases; and improves the correctness of the reused test cases. Copyright © 2012 John Wiley & Sons, Ltd.

show abstract

Section: Our Approachmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Validating pragmatic reuse tasks by leveraging existing test suites

Makady

Walker

2012

Softw Pract Exp

View full text Add to dashboard Cite

show abstract

“…Elbaum et al [8,9,19], Kumar and Baar [25], and Orso et al [20,31] propose techniques that use serialization and deserialization for building unit tests from system tests. Their techniques capture interaction between modules during the execution of system tests to later replay for unit tests.…”

Section: Related Workmentioning

confidence: 99%

“…(handle ∈ handleToInstance)25 ... // complex code for deserializing cycles in graphs not shown26 else return handleToInstance(handle); (a) Example user code for serializing and deserializing in Java; (b) Serialization output for Java library; (c) Pseudo-code of deserialization from the readObject method in java.io.ObjectInputStream.…”

mentioning

confidence: 99%

CoDeSe

Gligoric

Marinov

Kamin

2011

Proceedings of the 2011 International Symposium on Software Testing and Analysis

View full text Add to dashboard Cite

Many tools for automated testing, model checking, and debugging store and restore program states multiple times. Storing/restoring a program state is commonly done with serialization/deserialization. Traditionally, the format for stored states is based on data: serialization generates the data that encodes the state, and deserialization interprets this data to restore the state. We propose a new approach, called CoDeSe, where the format for stored states is based on code: serialization generates code whose execution restores the state, and deserialization simply executes the code. We implemented CoDeSe in Java and performed a number of experiments on deserialization of states. CoDeSe provides on average more than 6X speedup over the highly optimized deserialization from the standard Java library. Our new format also allows simple parallel deserialization that can provide additional speedup on top of the sequential CoDeSe but only for larger states.

show abstract

Using AOP for Discovering and Defining Executable Test Cases

Cited by 2 publications

References 4 publications

Validating pragmatic reuse tasks by leveraging existing test suites

Validating pragmatic reuse tasks by leveraging existing test suites

CoDeSe

Contact Info

Product

Resources

About