Please add a progress indicator to the CLI test runner
Bug #1392123 reported by
Zygmunt Krynicki
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Next Generation Checkbox (CLI) |
Fix Released
|
Medium
|
Maciej Kisielewski | ||
PlainBox (Toolkit) |
Fix Released
|
Medium
|
Maciej Kisielewski |
Bug Description
During the sprint in Taipei we learned that it would be useful to display basic session "progress", before every test. There is no concrete design but I think it would be enough to add a one-liner that says what's the completion percentage, what is the elapsed time and what is the estimated remaining time
Related branches
lp:~kissiel/checkbox/fix-1392123
- Zygmunt Krynicki (community): Approve
-
Diff: 20 lines (+1/-2)1 file modifiedplainbox/plainbox/impl/commands/inv_run.py (+1/-2)
Changed in checkbox-ng: | |
status: | New → Confirmed |
Changed in plainbox: | |
status: | New → Confirmed |
tags: | added: ce-qa-concern |
Changed in checkbox-ng: | |
importance: | Undecided → Medium |
Changed in plainbox: | |
importance: | Undecided → Medium |
Changed in checkbox-ng: | |
assignee: | nobody → Maciej Kisielewski (kissiel) |
status: | Confirmed → In Progress |
Changed in plainbox: | |
assignee: | nobody → Maciej Kisielewski (kissiel) |
status: | Confirmed → Fix Committed |
Changed in checkbox-ng: | |
status: | In Progress → Fix Committed |
Changed in checkbox-ng: | |
milestone: | none → 0.21 |
Changed in plainbox: | |
milestone: | none → 0.22 |
Changed in checkbox-ng: | |
milestone: | 0.21 → 0.20 |
Changed in checkbox-ng: | |
status: | Fix Committed → Fix Released |
Changed in plainbox: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
There is a new line in front of every job run:
-------------[ Running job 21 / 114. Estimated time left: unknown ]-------------
Unfortunately, if one of the job in the test plan does not have an `estimated_ duration` parameter in its definition, it is impossible for Plainbox to compute the remaining estimated time.
This can be fixed by updating the jobs to make sure all of the ones we use in the test plans have an `estimated_ duration` parameter.
Also, when resuming a session, new statistics are displayed including progress indications:
=== ======= ======= ======= =====[ Session Statistics ]====== ======= ======= ======= ==
This session is about 1.72% complete
Estimated duration cannot be determined for automated jobs.
Estimated duration is 3920.00 for manual jobs.
Size of the desired job list: 116
Size of the effective execution plan: 116