Skip to main content
Software Engineering

Return to Answer

Grammatical correction
Source Link
edit approved Mar 10, 2012 at 5:52
thegreendroid
edit approved Mar 10, 2012 at 5:52
thegreendroid
  • 369
  • 2
  • 13

Why would you want to allow a build to succeed with known defects?

Because sometimes, you have time constraints. Or because the bug is so minor that it doesn'tisn't really worth delaying the shipment of the product for a few days needed to unit test and fix it.

Also, what's the point in breaking the buildsbuild intentionally every time you find a bug? If you found it, fix it (or assign it to the person who will fix it), without disturbing your whole team. If you want to remember to fix a bug, then you need to mark it as very important in your bug tracking system.

Why would you want to allow a build to succeed with known defects?

Because sometimes, you have time constraints. Or because the bug is so minor that it doesn't really worth delaying the shipment of the product for a few days needed to unit test and fix it.

Also, what's the point in breaking the builds intentionally every time you find a bug? If you found it, fix it (or assign it to the person who will fix it), without disturbing your whole team. If you want to remember to fix a bug, then you need to mark it as very important in your bug tracking system.

Why would you want to allow a build to succeed with known defects?

Because sometimes, you have time constraints. Or the bug is so minor that it isn't really worth delaying the shipment of the product for a few days needed to unit test and fix it.

Also, what's the point in breaking the build intentionally every time you find a bug? If you found it, fix it (or assign it to the person who will fix it), without disturbing your whole team. If you want to remember to fix a bug, then you need to mark it as very important in your bug tracking system.

Source Link
Arseni Mourzenko
Arseni Mourzenko
  • 139.4k
  • 32
  • 359
  • 544

Why would you want to allow a build to succeed with known defects?

Because sometimes, you have time constraints. Or because the bug is so minor that it doesn't really worth delaying the shipment of the product for a few days needed to unit test and fix it.

Also, what's the point in breaking the builds intentionally every time you find a bug? If you found it, fix it (or assign it to the person who will fix it), without disturbing your whole team. If you want to remember to fix a bug, then you need to mark it as very important in your bug tracking system.