Information Processing Letters
PLDI '90 Proceedings of the ACM SIGPLAN 1990 conference on Programming language design and implementation
Reducing wasted development time via continuous testing
ISSRE '03 Proceedings of the 14th International Symposium on Software Reliability Engineering
An experimental evaluation of continuous testing during development
ISSTA '04 Proceedings of the 2004 ACM SIGSOFT international symposium on Software testing and analysis
GZoltar: an eclipse plug-in for testing and debugging
Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering
MZoltar: automatic debugging of Android applications
Proceedings of the 2013 International Workshop on Software Development Lifecycle for Mobile
Recovering test-to-code traceability using slicing and textual analysis
Journal of Systems and Software
Hi-index | 0.00 |
Unit testing is essential in the agile context. A unit test case written long ago may uncover an error introduced only recently, at a time at which awareness of the test and the requirement it expresses may have long vanished. Popular unit testing frameworks such as JUNIT may then detect the error at little more cost than the run of a static program checker (compiler). However, unlike such checkers current unit testing frameworks can only detect the presence of errors, they cannot locate them. With EZUNIT, we present an extension to the JUNIT ECLIPSE plug-in that serves to narrow down error locations, and that marks these locations in the source code in very much the same way syntactic and typing errors are displayed. Because EZUNIT is itself designed as a framework, it can be extended by algorithms further narrowing down error locations.