archeman

• Jun 12th, 2007

 

I know of two definitions for a Deferred bug

1) Most Common: A defect that is confirmed by the team to be a bug but the effort to correct it at this time exceeds the ROI (Return On Investment). This can often be the case when a re-design is scheduled for that area of the application, or if technology barriers exist that make correction of the bug prohibative.

2) Least Common:
a) A defect that has been detected early in the development process before the code is ready to submit to QA for formal test.
b) A defect that has been submitted by the QA group that covers behaviors not well defined by requirements documentation. These bugs may remain in a deferred state awaiting furthor review by all interested team parties

QA

• Jul 20th, 2017

 

What execution status should Test Case have when it is associated to a deferred defect?