Software Development Cross Solution - Index of - Free

Continuous integration (CI)
Test-driven development
(TDD)
Each class is listed individually
(broken up by package) One measure of testing
coverage is line coverage-what
percentage of the total lines
of code are we executing
through our tests?
Test coverage
Another measure is
branch coveragehat
percentage of
the alternate flows
(ifs, elses, etc.) are
we executing?
The repository always builds
because compilation and testing are part of check-in, and the
code in the repository always works.
What does this technique offer?
Nobody checks out code and
finds out it doesn’t work, or doesn’t compile. Bug reports
should go down, since code must pass tests to be checked in.
How do you know if it worked?
A way to ensure your code
is testable from the very beginning of development. Also
introduces test-friendly patterns into your code.
What does this technique offer?
Fewer bugs because testing
starts earlier. Better coverage, and every line of code
matters. Possibly better design, and less legacy code.
How do you know if it worked?
How do you know if it worked?
the real world
What does this technique offer? Better metrics on how much
code is being tested and used. A way to find bugs because they
usually exist in untested and uncovered code.
Bugs becomes focused on edge
cases because the main parts of code are well-tested. Less
unused or “cruft” code that’s uncovered and not useful.
Download at WoweBook.Com
you are here 4 423