Abstract
Unit testing is an important quality assurance method but a challenge in the context of legacy code. We share our experiences in trying to create tests for existing code by means of two examples from a large industrial software system and list common testability issues observed. Although much effort and resources have been invested, the retrofitting of unit tests was only partially successful. Our findings are that the probability that code without initial tests will ever get covered by unit tests is very low. Only the existence of unit tests ensures testability of the code under test. Besides finding defects unit tests also ensure modular design, which is the base for reuse, maintainability and testability. As a consequence, code and tests should be written together, ideally in a test-driven way.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
