Software Development Cross Solution - Index of - Free

CHAPTER 7
your software development toolbox
Development Techniques
There are different views of your
system, and you need to test them all
Testing has to account for success cases
as well as failure cases
Automate testing whenever possible
Use a continuous integration tool to
automate building and testing your code
on each commit
274 Chapter 7
Tools for your Software Development Toolbox
Software Development is all about developing
and delivering great software. In this chapter,
you learned about several techniques to keep you
on track. For a complete list of tools in the book,
see Appendix ii.
Development Principles
Testing is a tool to let you know where
your project is at all times
Continuous integration gives you
confidence that the code in your
repository is correct and builds properly
Here are some of
the key techniques
you learned in this
chapter...
Code coverage is a much better metric
of testing effectiveness than test count
... and some of the
principles behind
those techniques.
Download at WoweBook.Com
�
�
�
�
�
Using Continuous
Integration tools means
something is always
watching over the quality of
the code in the repository.
Automated testing can be
addictive. You still get to
write code, so it’s fun. And
sometimes you break things.
Also fun.
Make the results of your
continuous integration builds
and coverage reports public
to the team—the team owns
the project and should feel
responsible.
Have your continuous
integration tool fail a build if
an automated test fails. Then
have it email the committer
until they fix it.
Testing for overall
functionality is critical
to declaring a project as
working.