Hi John,
A Test Case can be blocked by a defect. For instance, let's say that I have Test Case to "View Order Report". Before I can view the order report, I need to log in. But, there is a defect that prevents logging in to my app. My "View Order Report" test case is now blocked by this defect.

If you're fully integrated with RTC, including builds, then when the log-in defect gets resolved and delivered in a build, RQM can "notice" that event and automatically unblock your Test Case now that you should be able to log in.

Hope that helps.
John

Environment: RQM 2.0 connected to RTC 2.0

Can some one please clarify the definition for "Blocking"..

I think it means that "something" is blocking the execution of the Test Case (not that the Test Case is blocking something else)..

Further; it seems that "Blocking" in RQM/RTC has been specifically implemented to allow build notification to RQM to trigger the automatic unblocking of blocked TCs / TERs... it seems then, that "Blocking" actually means, & is equivalent to, "Failed".. if this is the case, then in an environment where RQM 2.0 connected to RTC 2.0, it would seem that all test executions should be set to blocked on failure, .. if one want to avail of the automatic unblocking functionality?