Now, I'd like to summarize the results. The most significant idea is that all team members have to take the responsibility. In fact, even when white-box testing is provided, there's no opportunity to predict all possible situations of software use. There’s no way to create so many different test scenarios to describe all possible variants of software use by the deadline. However, every user working with the software creates his or her own special scenario. The more users work with the product, the more use variants they propose. So, there is a greater opportunity to find new bugs.
Perfect software cannot be written. Perfect tests should cover as many variants of software use as possible. The number of bugs found by the end-user will be reduced, but the bugs won't disappear at all, and what is the most important, no particular team member is to blame.
That's a usual working situation, and the task of the highest priority is to fix bugs and to provide a user with a better product. That's the guarantee of high quality.
1 comment:
Very Nice and useful article. Thanks for sharing this. Thanks for the article Ian, excellent stuff.
You can get info on cross browser testing tools as well with some guidelines with different.
Post a Comment