Manual tests should show description/steps/verification at once
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PlainBox (Toolkit) |
Fix Released
|
High
|
Unassigned |
Bug Description
Bug lp:1453067 was fixed, but now (plainbox v0.22) a tester has to press ENTER before being able to see a manual test steps and verification parts. Example with the docking tests using the new fields [1]
-------------[ Running job 21 / 114. Estimated time left: unknown ]-------------
-------
ID: 2013.com.
Category: 2013.com.
Purpose:
This test will check the HDMI port(s) on the dock.
Pick an action
=> press ENTER to continue
c => add a comment
s => skip this job
q => save the session and quit
[csq]: <ENTER>
Steps:
Skip this test if the dock does not have a HDMI port.
1. Connect a display (if not already connected) to the HDMI port on the dock
2. Repeat step 1 for each additional HDMI port, if any
Verification:
Was the desktop displayed correctly on both screens?
Please decide what to do next:
outcome: job needs verification
comments: UNSET
Pick an action
c => add a comment
p => set outcome to pass
f => set outcome to fail
s => set outcome to skip
=> set suggested outcome [job failed]
[cpfs]:
It would be better if, for manual tests, the whole block was displayed at once, without having to press ENTER in order to see Steps/Verification, such as:
-------------[ Running job 21 / 114. Estimated time left: unknown ]-------------
-------
ID: 2013.com.
Category: 2013.com.
Purpose:
This test will check the HDMI port(s) on the dock.
Steps:
Skip this test if the dock does not have a HDMI port.
1. Connect a display (if not already connected) to the HDMI port on the dock
2. Repeat step 1 for each additional HDMI port, if any
Verification:
Was the desktop displayed correctly on both screens?
Please decide what to do next:
outcome: job needs verification
comments: UNSET
Pick an action
c => add a comment
p => set outcome to pass
f => set outcome to fail
s => set outcome to skip
=> set suggested outcome
[cpfs]:
[1]: http://
Changed in plainbox: | |
milestone: | none → 0.22 |
Changed in plainbox: | |
status: | Confirmed → Fix Committed |
importance: | Undecided → High |
tags: | added: cqa-verified |
Changed in plainbox: | |
status: | Fix Committed → Fix Released |
I re-run a subset of the docking test plan using boxer (`boxer run stella`, which creates its own CLI launcher) in order to check the behaviour with different kinds of plugins (manual, shell, user-interact and user-interact- verify) :
dock/docking (manual) playback- headphones (user-interact- verify) verify) storage- automated (shell)
dock/audio-
dock/usb-HID (user-interact-
dock/usb-insert (user-interact)
dock/usb-remove (user-interact)
dock/usb-
The behaviour was correct for all of them (see attachement showing the screen output).
I also re-run another test plan and the behaviour is the same as with previous versions, so there is no regression.
→ Problem fixed!