Dynamic Unit Test Extraction Via Time Travel Debugging for Test Cost Reduction

Bach, Thomas; Pannemans, Ralf; Haeussler, Johannes; Andrzejak, Artur

doi:10.1109/icse-companion.2019.00093

Cited by 3 publications

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In addition to the general aspect, code coverage also allows us on a technical level to apply techniques from research work to reduce test code or to improve quality [1,4,8]. However, we found that we must carefully check the usefulness of such techniques.…”

Section: Code Coveragementioning

confidence: 99%

Testing Very Large Database Management Systems: The Case of SAP HANA

et al. 2022

Self Cite

View full text Add to dashboard Cite

Software Testing is an established activity in the software development process to ensure and improve the quality of a software. Consequently, there exists a wide range of literature, popular information, and even multiple ISO standards covering this topic. However, we found that testing very large database management systems (DBMS) requires special adaptations of the generally available guidance for software testing and requires to solve specific challenges that may not be relevant for other areas or smaller software projects. We therefore discuss the testing of SAP HANA, a very large software project with millions of lines of code, to share insights about our approach, best practices, and unsolved challenges that are open for further research.

show abstract

Section: Code Coveragementioning

confidence: 99%

Testing Very Large Database Management Systems: The Case of SAP HANA

et al. 2022

Self Cite

View full text Add to dashboard Cite

show abstract

“…Bach et al [2] propose to extract unit test cases from system test cases through the reverse execution (called time travel debugging) of a program flow for reconstructing object creation and modification statements from the source code. The approach also uses differential analysis to identify the test statements from which the unit test case will be extracted.…”

Section: Related Workmentioning

confidence: 99%

Log-based slicing for system-level test cases

Messaoudi

Shin

Panichella

et al. 2021

Proceedings of the 30th ACM SIGSOFT International Symposium on Software Testing and Analysis

View full text Add to dashboard Cite

Regression testing is arguably one of the most important activities in software testing. However, its cost-effectiveness and usefulness can be largely impaired by complex system test cases that are poorly designed (e.g., test cases containing multiple test scenarios combined into a single test case) and that require a large amount of time and resources to run. One way to mitigate this issue is decomposing such system test cases into smaller, separate test cases-each of them with only one test scenario and with its corresponding assertions-so that the execution time of the decomposed test cases is lower than the original test cases, while the test effectiveness of the original test cases is preserved. This decomposition can be achieved with program slicing techniques, since test cases are software programs too. However, existing static and dynamic slicing techniques exhibit limitations when (1) the test cases use external resources, (2) code instrumentation is not a viable option, and (3) test execution is expensive.In this paper, we propose a novel approach, called DS3 (Decomposing System teSt caSe), which automatically decomposes a complex system test case into separate test case slices. The idea is to use test case execution logs, obtained from past regression testing sessions, to identify "hidden" dependencies in the slices generated by static slicing. Since logs include run-time information about the system under test, we can use them to extract access and usage of global resources and refine the slices generated by static slicing.We evaluated DS3 in terms of slicing effectiveness and compared it with a vanilla static slicing tool. We also compared the slices obtained by DS3 with the corresponding original system test cases, in terms of test efficiency and effectiveness. The evaluation results on one proprietary system and one open-source system show that DS3 is able to accurately identify the dependencies related to the usage of global resources, which vanilla static slicing misses. Moreover, the generated test case slices are, on average, 3.56 times faster than original system test cases and they exhibit no significant loss in terms of fault detection effectiveness. CCS CONCEPTS• Software and its engineering → Software testing and debugging; Automated static analysis.

show abstract

Microservice Debugging with Checkpoint-Restart

Merino

Otero

2023

2023 IEEE Cloud Summit

View full text Add to dashboard Cite

Dynamic Unit Test Extraction Via Time Travel Debugging for Test Cost Reduction

Cited by 3 publications

References 6 publications

Testing Very Large Database Management Systems: The Case of SAP HANA

Testing Very Large Database Management Systems: The Case of SAP HANA

Log-based slicing for system-level test cases

Microservice Debugging with Checkpoint-Restart

Contact Info

Product

Resources

About