Software testing in the real world: improving the process
Software testing in the real world: improving the process
Performance testing of software systems
Proceedings of the 1st international workshop on Software and performance
Experience with Performance Testing of Software Systems: Issues, an Approach, and Case Study
IEEE Transactions on Software Engineering
An empirical methodology for introducing software processes
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
Software Reliability Engineered Testing
Software Reliability Engineered Testing
Certifying Software for High-Assurance Environments
IEEE Software
An empirical evaluation of system and regression testing
CASCON '02 Proceedings of the 2002 conference of the Centre for Advanced Studies on Collaborative research
| Hi-index | 0.00 |
The traditional software development life cycle considers testing to be an activity that occurs between the implementation phase of development and software release [4]. With this approach any testing subsequent to release is done in reaction to failures reported by software users. The realities of software in operation however causes questions about this approach to arise. Adams [1] showed that organizations developing significant software applications often provide several fixes after their software has been released as the result of errors found in the field. This work also showed that the most serious and frequently recurring errors are usually found by users soon after a product has been released. These are referred to by Adams [1] as virulent errors. The negative effects of remaining defects implies that post-release activities should be proactive. These post-release activities must include continued testing by the vendor to find errors even after release. This paper proposes a solution to this requirement.