Prior to release 2.30, a defect could be put into an appropriate status as required by the user. However, this capability did not make it clear why the defect was put into that status in the first place. In particular, when defects were closed, it was often wanting to be reported whether it was closed because of such reasons as that the problem was resolved, the problem was expected, the problem could not be understood or a false negative was identified.

For this reason, it is now possible to configure and specify a “closure reason” against the defect which can be set when the defect is worked by the testing team.

Closure reasons are configured in table /BTI/AUT_C_ which can be maintained via transaction SM30 in the central system.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment