Checkbox-qt: When checkbox is running an automated test, previous test interface should not appear.
Bug #1012377 reported by
Jeff Marcom
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Checkbox-qt: When checkbox is running an automated test, previous test interface should not appear.
Problem:
Automated test is running in the top of test window pane with progress bar, while un-related test comments/
Example:
cpu_test is running while audio/microphone test instructions and result buttons are still present.
Steps to Reproduce: (Issue was seen with checkbox-qt interface):
1.) Start checkbox
2.) run through tests
Expected Result:
Automated tests should run in their own window, or refresh/restore active window.
Related branches
lp://staging/~jeffmarcom/checkbox/1012377
- Daniel Manrique (community): Approve
- Jeff Marcom (community): Needs Resubmitting
- Brendan Donegan (community): Needs Fixing
-
Diff: 48 lines (+15/-0)2 files modifieddebian/changelog (+2/-0)
qt/frontend/qtfront.cpp (+13/-0)
lp://staging/~sylvain-pineau/checkbox/0.15
- Daniel Manrique (community): Approve
-
Diff: 1477 lines (+506/-529) (has conflicts)1 file modifieddebian/changelog (+506/-529)
Changed in checkbox: | |
importance: | Low → Medium |
Changed in checkbox: | |
status: | New → Incomplete |
assignee: | Marc Tardif (cr3) → nobody |
Changed in checkbox: | |
status: | In Progress → Fix Committed |
Changed in checkbox: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Agreed, seeing the previous manual tests while one or more shell tests are running doesn't make sense. However, I'm not clear on the solution you propose.
You first suggest "tests should run in their own window", do you mean a popup window? If so, should a new popup window open and close for each shell test or should one popup window refresh itself as long as there are shell tests running?
You also suggest "refresh/restore active window", what should it contain?
While answering these questions, I'd appreciate if you could consider the two extreme use cases where you have few shell tests that take a lot of time or you have many shell tests that take little time. So, for a popup window that opens and closes, the user experience might just look like windows flashing by if the tests take little time.