Software Development Cross Solution - Index of - Free

Top 10
Traits of
Effective
System
Testing
Good, frequent communication between the customer,
development team, and testing team.
ending an iteration
Know the starting and ending state of the system. Make
sure you start with a known set of test data, and that the data ends up
exactly like you’d expect it at the end of your tests.
Document your tests. Don’t rely on that one awesome tester
who knows the system inside and out to always be around to answer
questions. Capture what each tester is doing, and do those same things
at each round of system testing (along with adding new tests).
Establish clear success criteria. When is the system good enough
to go live? Testers can test forever—know before you start what it
means to be finished. A zero-bug-bounce (when you get to zero
outstanding bugs, even if you bounce back up after that) is a good sign
you’re getting close.
Good, frequent communication between the customer,
development team, and testing team.
Automate your testing wherever possible. People just aren’t
great at performing repetitive tasks carefully, but computers are. Let the
testers exercise their brains on new tests, not on repeating the same five
over and over and over again.
A cooperative dynamic between the development team and
testing team. Everyone should want solid, working software that they
can be proud of. Remember, testers help developers look good.
A good view of the big picture by the testing team. Make sure
that all your testers understand the overall system and how the pieces fit
together.
Accurate system documentation (stories, use cases, requirements
documents, manuals, whatever). In addition to testing docs, you should
capture all of the subtle changes that happen during an iteration, and
especially between iterations.
Good, frequent communication between the customer,
development team, and testing team.
Download at WoweBook.Com
you are here 4 333