Software Development Cross Solution - Index of - Free

This is
usually
called
acceptance
testing.
effective system testing
v Below are some different approaches to testing, all of which
involve just one cycle of iterations. What are some good things
about these approaches? What are some bad things?
Iteration
1
If you only have one team to work with, this approach isn’t too bad. One big drawback is that serious
system testing starts very late in the process. If you take this approach, it’s critical that the results
of each iteration get out to at least a set of beta users and the customer. You can’t wait until the
end of the third iteration to start any testing and collecting feedback.
This approach also works pretty well if you need to do formal testing with the customer before they
sign off on your work. Since you’ve been doing automated testing during each iteration and releasing
your software to users at the end of each iteration you have a pretty good sense that you’re building
the right software and it’s more or less working as expected. The test iteration at the end is where
the formal “check-off” happens before you start looking at Version 2.0.
Iteration
1
This approach requires a lot of iterations, and 50% of your time is spent in testing. It really
would only work in situations where your customer is willing to expend a lot of time on testing and
debugging. Let’s say that your customer is thrilled with the idea of monthly releases to the public;
it keeps the site fresh and dynamic in their users’ eyes. However, the customer insists on a formal
validation process before the code goes anywhere. If you don’t have a separate acceptance- and
system-testing team, you’re going to be looking at a situation a lot like this.
332 Chapter 9
Iteration
2
Test
I1
Iteration
3
Iteration
2
Download at WoweBook.Com
Test
Iteration
Test
I2
Bug fixes
Iteration
3...