Closed
Bug 321120
Opened 20 years ago
Closed 20 years ago
Make completed testcases noticible upon return to an incomplete group.
Categories
(Webtools Graveyard :: Litmus, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: tracy, Assigned: coop)
Details
right now the testcase ID#'s in the run and results do not match. This is because the testcase# in a run is subgroup dependent. For example, in the Firefox smoketests, there are 4 tescases in the sub group for Installation and Startup. there are 26 in the group for Functionality and 2 in Uninstall. When in a test run the test cases are numbered within that subgroup. 1-4, 1-26, 1-2 for each of the subgroups in the smoketest suite. However, when you go to the results for a smoketest run. The results are number 1-32.
Is it possible to have the testcase ID# in a run not be subgroup dependent?
Discovered this when I had thought I'd completed the Functionality group only to see that it was 96% complete. I still had one testcase to do. So I ran a search and discover it was testcase 13 that was missing. I went back into the run and did testcase 13 in the Functionality subgroup only to find that I had just run test case 17 again. The testcase I should have run was Functionality test case #9.
But it's asthetically prettier to have each subgroup display 1 to whatever instead of being test suite dependent. The underlying issue is being able to easily tell which testcases have been run when returning to a suite that is partially complete. changing summary :-)
Possible solution: in the testcase "strip" display an icon for the status of the testcase. Leave it blank if not run. Use traffic light icon; green for passed, red for failed and yellow for unclear. A traffic light icon pressent would mean the you had already run the testcase.. I know this changes the way you handle going back to the test run. Currently you reset everything to not run.
| Reporter | ||
Comment 1•20 years ago
|
||
coop, don't disable the testcase upon submission.
| Assignee | ||
Comment 2•20 years ago
|
||
What I'm hearing is that we _shouldn't_ disable either testcases or even subgroups, but simply make it easy for the user to see that "you have already completed this subgroup/testcase." We should allow the user to re-test the same areas of functionality if they choose/require, e.g. their first testing pass was invalid due to faulty config, bad instructions, etc.
We already do this for subgroups, so it is a matter of extending this to individual testcases and perhaps making the "already run" status more obvious.
| Assignee | ||
Updated•20 years ago
|
Priority: -- → P2
| Reporter | ||
Comment 3•20 years ago
|
||
what about changing the steps to perform background color to the matching status color, display any comments from previous submission and bug numbers in there respective text fields?
or even change the test case listing background color, that way when you look at the display you can see all those that are already tested and go right to the untested ones. this is the darker grey background currently.
| Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Updated•20 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•19 years ago
|
QA Contact: ccooper → litmus
Updated•10 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•