Software Development Cross Solution - Index of - Free

Q: So how often should we run our entire test
suite?
A: This is really up to you and your team. If you’re
happy with running your full test suite once a day, and
know that any regression bugs will only be caught
once a day, then that’s fine. However, we’d still
recommend you have a set of tests that can be run
much more frequently.
Hmm, won’t testing everything every time make
testing take a long time? Isn’t there a way of tuning
things so that developers can regression-test everything
when they need to, and just fit testing in manually
Tailor your test suites to suit the occasion
testing and continuous integration
It’s unfortunately true that large unit test suites become ungainly and,
therefore, tend to get used less. One technique is to break out fast and
slow tests so that a developer can run all the fast tests often while they are
changing and adding code, but only run the full suite when they think they
need to.
What tests fall into the fast or slow categories is really up to your particular
project, and which category specific tests fall into can change depending on
the development work that you are doing. For example, if you have barelyever-changes
code that takes a long time to test, then that would be a good
candidate for the slow test suite. However if you were working on code that
might well impact the barely-ever-changes code, then you might consider
moving its tests into the fast test suite while you are working those changes.
Let’s try it out with a popular free testing framework for Java, called JUnit.
To download the JUnit framework,
go to http://www.junit.org
Download at WoweBook.Com
You can also speed
up slow tests using
mocks; see Chapter 8
for more on those.
Keep the time it takes to
run your tests as short as
possible. The longer a test
suite takes to run, the less
often it is likely to be run!
you are here 4 249