Blocking TER vs Blocked State of Test Execution Result
In RQM, user can set the test execution state to "Blocked" and associate the TER with a blocking defect. I noticed two columns in the TER list table. One is called "Last Result" and the other one is called "Blocking Status". If I mark a TER as Blocked in the Execution Result page. Then I can see the "Lase Result" column is changed. But only when I use Manage Blocking Defects function to add Blocking defect to this ER, then the "Blocking Status" changed to blocked.
So my questions is: What are the differences between the two attributes? If an ER's last result is shown as "Blocked" should the "Blocking Status" also be automatically updated as blocked? Why do we use two columns? This adds extra work for testers and may cause confusion. For example, user can set an ER result as "passed" while still have the Blocking Status show as "Blocked". There is no mechanism in RQM to force that to be consistent.
Anyone knows what is the purpose of having a "Blocking Status" column for TER? Thanks.
So my questions is: What are the differences between the two attributes? If an ER's last result is shown as "Blocked" should the "Blocking Status" also be automatically updated as blocked? Why do we use two columns? This adds extra work for testers and may cause confusion. For example, user can set an ER result as "passed" while still have the Blocking Status show as "Blocked". There is no mechanism in RQM to force that to be consistent.
Anyone knows what is the purpose of having a "Blocking Status" column for TER? Thanks.
One answer
Ian,
The Blocking status column shows if there are blocking defects associated with a TER. There is a button at the top of the table to view the blocking defects and change their status if required. The blocking status changes automatically if the defects are resolved/closed.
The last result shows the verdict of the ER that was generated when the TER was last executed.
So the Blocking status column doesn't have anything to do with the verdict of the latest ER for that TER.
You could have a blocking defect from a previous ER and have the latest ER as passed.
If it really causes confusion, there is always the option to hide the column from the table
Pratik
Thanks Pratik. So the blocking status is just an indicator and has nothing to do with the test report? For example, A test execution record has 5 points. If I pass 3, block 2 and set the result state as "Blocked". But I do not use Managing Blocking defect to add the blocking status, and the Blocking Status column is empty. In this case, my test report will still show I have 2 points blocked?
If I do it other way around, that is I passed 3 points but failed 2 points. and I set my last test result as failed. Also, I use Manage Blocking defect to add a blocking defect to the ER. Now for this ER, the result is "Failed" the blocking status is "Blocked". I suspect I will not see anything related to blocking in the test report because the test result is "Failed" not "Blocked". So what's the point to have Blocking Status in this case?
Thanks.