Prevent Defects

How will you prevent defects from a tester point of view?

Questions by savitha88

Editorial / Best Answer

vkaranthaa  

  • Member Since Apr-2010 | Apr 19th, 2010


Defect prevented at the early stage of the lifecycle saves lot of money and effort to the company. There are different ways of preventing defects. Some examples are as follows:
a. Use previously logged defects and analyze the pattern incase its a existing application / system
b. Review and inspections of the analysis, design and coding artifacts to make sure they adhere to proper guidelines
c. Review of test cases written by testing team from development team and Business users / analysts to avoid any gap
d. Have testing from development team of the integrated application before delivering it to the testing team.

We have used all these and have found them to be effective in reducing no. of defects.

Showing Answers 1 - 6 of 6 Answers

Pat Woods

  • Apr 16th, 2010
 

Testing cannot in and of itself prevent defects, only discover them. However, if the intended tests are shared with both the client and  the development team, any deviation in perception between the developers and the client regarding the expected can be explored as part of a total quality assurance effort. In addition,the quality assurance team can participate in design, code and other artifact reviews to raise issues from the testing perspective that may not be readily apparent to the development team. Finally, the test team reviews the requirements for any ambiguities or inconsistancies to mitigate any misunderstanding of the desired results.

vkaranthaa

  • Apr 19th, 2010
 

Defect prevented at the early stage of the lifecycle saves lot of money and effort to the company. There are different ways of preventing defects. Some examples are as follows:
a. Use previously logged defects and analyze the pattern incase its a existing application / system
b. Review and inspections of the analysis, design and coding artifacts to make sure they adhere to proper guidelines
c. Review of test cases written by testing team from development team and Business users / analysts to avoid any gap
d. Have testing from development team of the integrated application before delivering it to the testing team.

We have used all these and have found them to be effective in reducing no. of defects.

There could be several ways to prevent defects in early stages:

1. First and most important thing is requirement elaboration.  There might be some ambiguities between your side and client side and that may result in some bugs.  And also it is more important to be in sync between dev and QA team.  QA team might be logging a bug which could be considered as invalid or some other resolution just due to the misunderstanding and miscollection of requirements.

2. If requirement is all clear and you have run with some of the iterations, then in that case with limited time limit, you can go for previous bugs and check them all first .This is when product is in initial stage.  I mean regular CRs are made and we cant go for automation.

3. If product is almost stable in terms of requirements then we can use any automation tool for quick regression test.  It would do both-wud save time and wud make us available with early bugs finding.

4. Except that another and most effective thing can be done when we go for UNIT testing.  It would save alot time when developer do these things from thier side and QA team is making automation testing from thier side after getting a intermediate build.

Simple concepts to be taken.

1. Improve the standard checklists for designers as per clients requirements.
2. Unit testing should be used twice by the developers.
3. There should be some walkthrough time to time with developers about the exact knowledge of client requirements.
4. Each find bugs should be in so much details and regression effect should also be described there.

naveenanand

  • Nov 11th, 2010
 

1) Both the developers and testers should have sound knowledge about the requirements of the customer.
2) Both verification and validation should be perfect.
3) Testers should have analizing skills, once the bugs are raised and they should ensure that the same kind of bugs are not raised and clear commnication should be sent to developement team. 

  Was this answer useful?  Yes

chaitu83

  • Nov 25th, 2010
 

  • Testers should be involved in discussions with business analysts and Development team in the design phase to have clear understanding of the requirements.
  • Prepared test cases should be reviewed with Business analysts and Development  teams to understand if any requirement is missed out.
  • In case of existing application, previously raised defects should be checked to see if the New functionality is causing any of those defects again.

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions