By Topic

Tool Support for Change-Centric Test Development

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

3 Author(s)
Jan Wloka ; Rutgers University, New Brunswick ; Einar Hoest ; Barbara G. Ryder

Testing increases confidence in software's correctness, completeness, and quality. By executing a test on a program, developers can check the outcome against the program's specification to identify faults. Various testing levels can serve different purposes during development-for example, unit and integration testing let developers test an implementation and its effects on existing functionality. In test-driven development, a unit test acts as a functionality specification before implementation, letting developers apply only the code necessary to pass the test. Applying change impact analysis to test-driven development provides software designers quantitative feedback they can use to meet a coverage goal and avoid unanticipated change effects.

Published in:

IEEE Software  (Volume:27 ,  Issue: 3 )