COMP 4004 Lecture Notes - Lecture 1: Subroutine, Maintainability, Code Coverage

• School: Carleton University
• Department: Computer Science
• Course: COMP 4004
• Professor: Jean-Pierre Corriveau

Document Summary

Test driven development is a specific agile process. Pick a feature, write a test, then right the code until test passes. Refactor and decouple objects, re-running tests to make sure they still pass. Test driven development by kirrily robert: the problem, finding good balance, no silver bullet, no magic recipe, (cid:862)to add(cid:396)ess all the fa(cid:272)ets of testi(cid:374)g p(cid:396)o(cid:271)a(cid:271)l(cid:455) (cid:374)eed at least (cid:1005)(cid:1006) tools. The (cid:373)o(cid:396)e tools (cid:455)ou use, the worse off you are. A good test i(cid:374)sti(cid:374)(cid:272)ti(cid:448)el(cid:455) k(cid:374)o(cid:449)s (cid:449)hat to test a(cid:374)d ho(cid:449) to fi(cid:374)d (cid:449)a(cid:455)s to break a system: hard to measure how much was tested and how well they tested. It is a (cid:373)(cid:455)th that soft(cid:449)a(cid:396)e (cid:395)ualit(cid:455) is (cid:862)i(cid:374)sti(cid:374)(cid:272)ti(cid:448)e(cid:863) a(cid:374)d ha(cid:396)d to (cid:373)easu(cid:396)e: s/w testing is about running code to check its behavior. It should pass: example, design, the subroutine add() takes two arguments and adds them together.