Closed
Bug 552917
Opened 16 years ago
Closed 16 years ago
Re-arrange button for skipping tests
Categories
(Other Applications Graveyard :: QA Companion, defect)
Other Applications Graveyard
QA Companion
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: whimboo, Unassigned)
Details
Attachments
(1 file)
|
15.73 KB,
image/png
|
Details |
When running Litmus tests with the QAC add-on there is no way to skip tests. But this is needed when tests are offered which are not for the platform of the tester. Until know they mark tests as failed/unclear which is not the best way.
Can we please add another button to skip the test? That would be very helpful for our vetting process. Thanks.
Comment 1•16 years ago
|
||
Hey,
If you are using 1.2.2 you should see a 'Skip' button near the top of the 'Run Tests' tab. It is visible during the current test you are running.
Thanks Aaron. Exactly. We have that functionality already.
--> WFM
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 3•16 years ago
|
||
This button is really hard to discover. Why can't we move it right next to the other ones? That would make more sense and would be definitely better visible.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: QAC doesn't support skipping tests → Re-arrange button for skipping tests
(In reply to comment #3)
> This button is really hard to discover. Why can't we move it right next to the
> other ones? That would make more sense and would be definitely better visible.
What are you talking about? I don't understand this logic at all.
The Skip button is next to the "view testcase in litmus link (test case number)" the "testcase x out of y" subgroup mapping so you know where you are in the group, and the "Change Subgroup" button. This is done so that all the "test group navigation" operations are in one place on the UI. We do not want to break that flow becuase one of the key problems with the old UI was that the test navigation buttons were all over the place on the UI, which made it much more difficult to use.
We also turn the "test x of y" to have a green border when changing subgroups so that will call more attention to the navigation area. We could potentially do something like that with the skip button as well.
I'm not sure what buttons you're talking about putting it next to. The buttons at the bottom are for "test status" operations and "skip" is not a "test status".
Furthermore, when discussing this UI we should remember that the UI is specifically constrained to fit next to a user's firefox window on a small screen/low resolution. We cannot change the minimum required width and height of this window.
| Reporter | ||
Comment 5•16 years ago
|
||
Sorry for being so vague and less informative with my last comment. You are right with all your statements. I meant to place the skip button above or below the pass/unclear/failed buttons.
The problem we have at the moment is probably that the skip button is not colored. We use the default widget while the test result buttons are custom ones.
> We also turn the "test x of y" to have a green border when changing subgroups
> so that will call more attention to the navigation area. We could potentially
> do something like that with the skip button as well.
IMO it should have a constant color too. But if you think it's not worth the time please close the bug.
Comment 6•16 years ago
|
||
Closing. Don't think any changes are really necessary. Re-arranging with space constraints as it earlier was rather difficult and associating a colour with 'skip' doesn't make sense.
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → WORKSFORME
Comment 7•16 years ago
|
||
I agree with Clint/Aaron here. but we could make the skip button have -moz-appearance: none like the rest of the buttons though, so it will be grey but have a similar shape to the other buttons, really only a problem on Mac.
Updated•7 years ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•