Empirical Software Engineering
Towards a BPEL unit testing framework
Proceedings of the 2006 workshop on Testing, analysis, and verification of web services and applications
Validating UML simulation models with model-level unit tests
Proceedings of the 3rd International ICST Conference on Simulation Tools and Techniques
Comparing software measures with fault counts derived from unit-testing of safety-critical software
SAFECOMP'05 Proceedings of the 24th international conference on Computer Safety, Reliability, and Security
Hi-index | 0.00 |
Unit testing is a technique that receives a lot of criticism in terms of the amount of time that it is perceived to take and in how much it costs to perform. However it is also the most effective means to test individual software components for boundary value behavior and ensure that all code has been exercise adequately (e.g. statement, branch or MC/DC coverage). In this paper we examine the available data from three safety related software projects undertaken by Pi Technology that have made use of unit testing. Additionally we discuss the different issues that have been found applying the technique at different phases of the development and using different methods to generate those test. In particular we provide an argument that the perceived costs of unit testing may be exaggerated and that the likely benefits in terms of defect detection are actually quite high in relation to those costs.