Blog

Defect Prevention or Defect Detection

codefuse Uncategorized Leave a Comment

Prevention is better than a cure as they say. And this is true in software quality.

We’ve all seen the age-old graph of the rising cost of defects the later they are found in the project – an example can be seen here. But what about stopping those defects from ever appearing at all?

A number of techniques are available for this, but too many teams limit the remit of testers to strictly “testing the app” rather than testing things like requirements, or even the project process. Considerable quality gains can be made here.

A good starting point is “Static testing“. This is a great method to begin getting testers to think beyond running a bunch of scripts.

More advanced techniques such as Specification by Example (SBE) and Behaviour Driven Development (BDD) are also available to teams. These require more discipline but the results should be that you get things right first time.

No developer sets out to write buggy code. In the main bugs come from misunderstandings and poor communication. The defect prevention methods we have outlined here are all great ways to improve team understanding and find holes in the mediums of communication.

If you can achieve that, you won’t be needing so many cures later down the line!

Leave a Reply

Your email address will not be published. Required fields are marked *

Defect Prevention or Defect Detection

31 Dec 2015

Prevention is better than a cure as they say. And this is true in software quality.

We’ve all seen the age-old graph of the rising cost of defects the later they are found in the project – an example can be seen here. But what about stopping those defects from ever appearing at all?

A number of techniques are available for this, but too many teams limit the remit of testers to strictly “testing the app” rather than testing things like requirements, or even the project process. Considerable quality gains can be made here.

A good starting point is “Static testing“. This is a great method to begin getting testers to think beyond running a bunch of scripts.

More advanced techniques such as Specification by Example (SBE) and Behaviour Driven Development (BDD) are also available to teams. These require more discipline but the results should be that you get things right first time.

No developer sets out to write buggy code. In the main bugs come from misunderstandings and poor communication. The defect prevention methods we have outlined here are all great ways to improve team understanding and find holes in the mediums of communication.

If you can achieve that, you won’t be needing so many cures later down the line!

Leave a Reply

Your email address will not be published. Required fields are marked *

READY TO GET STARTED

Complete the form below and we’ll be in touch to discuss how we can help