ACM Transactions on Programming Languages and Systems (TOPLAS)
Watch what I do: programming by demonstration
Watch what I do: programming by demonstration
Analyzing Regression Test Selection Techniques
IEEE Transactions on Software Engineering
Continuous execution: the VisiProg environment
ICSE '85 Proceedings of the 8th international conference on Software engineering
Incremental compilation in Magpie
SIGPLAN '84 Proceedings of the 1984 SIGPLAN symposium on Compiler construction
Prioritizing Test Cases For Regression Testing
IEEE Transactions on Software Engineering
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
Mock object creation for test factoring
Proceedings of the 5th ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering
Prioritizing JUnit Test Cases: An Empirical Assessment and Cost-Benefits Analysis
Empirical Software Engineering
Finding failure-inducing changes in java programs using change classification
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
MimEc: intelligent user notification of faults in the eclipse IDE
Proceedings of the 2008 international workshop on Cooperative and human aspects of software engineering
Proceedings of the 2012 International Symposium on Software Testing and Analysis
Integrating systematic exploration, analysis, and maintenance in software development
Proceedings of the 2013 International Conference on Software Engineering
Making offline analyses continuous
Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering
| Hi-index | 0.00 |
Continuous testing uses excess cycles on a developer's workstation to continuously run regression tests in the background, providing rapid feedback about test failures as code is edited. It reduces the time and energy required to keep code well-tested, and it prevents regression errors from persisting uncaught for long periods of time.