RQM Error Points allocation
Hi
We are using CLM 6.0, please let me know if this is a known bug:
As per the jazz.net post: https://jazz.net/forum/questions/227813/points-allocation-issues-rqm
When running TCER's in a test plan, points are allocated to passed and failed TCER's. Other results such as blocked and error should not be allocated points. So for e.g, in the status bar on the top of a test plan, if I have 10 TCER's with 5 passed, 3 fail and 2 blocked, the progress for TCER's should show 8 out of 10.
I have found that some of our blocked and error TCER's are being allocated a point which is causing that widget to be incorrect. After further investigation I see that if I run a TCER and pass a single step, but then continue to block all other steps, that TCER get allocated a point, BUT if I run a TCER and block all steps, that TCER gets allocated 0 points. This is very inconsistent because both have final results of Blocked, but one of the TCER's has 1 point allocated because of a single passed step during execution.
Please let me know if this is a bug and if a fix is available.
Thanks,
Leesen
|
One answer
Hi, Leesen
Comments
Leesen Padayachee
commented Mar 16 '17, 5:56 a.m.
Hi Don
We have many varying test scripts with numerous steps, therefore we wanted to use 1 point per test case to track the execution. How can weight distribution be set before execution takes place?
Thanks,
Leesen
Don Yang
commented Mar 16 '17, 7:15 p.m.
If I understand your question properly, you want to set weight as 1 for each test case regardless the steps. You can go to TCER and set weight to 1 in Summary section. When you set 1 point here, the passed/failed step will be calculated over the overall steps for example 3 passed/failed in 5 steps of script and you will get 1 point for passed/failed as a result(round up) and you will see that in plan's TCER progress bar.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.