subunit-trace provides no real-time status

Bug #1531209 reported by Federico Ceratto
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-testr
Triaged
Wishlist
Unassigned

Bug Description

Most testing tools provide configurable progress status e.g.:

Run with -v -v: print one dot "." for each test
Run with -v -v -v: print the name of the test being started (rather than printing on completion)

This would be useful to quickly spot slow/hanging tests instead of waiting for global timeouts (that can be a high value on large test suites)

Thanks.

summary: - Testr provides no real-time status
+ Testr provides no configurable progress status
summary: - Testr provides no configurable progress status
+ subunit-trace provides no real-time status
description: updated
Revision history for this message
Matthew Treinish (treinish) wrote :

The beginnings of inprogress displaying was in the original version of subunit-trace but they never quite worked so we removed that code. You can still see it some of the copy and pasted copies that existed before it was made into a proper entrypoint, for example:

https://github.com/openstack/taskflow/blob/master/tools/subunit_trace.py#L36-L82

I can see the value in having something like this, but it's never shown to be a priority. I would not be opposed to someone taking another crack at it, but we'd need testing upfront to verify it works.

Changed in os-testr:
importance: Undecided → Wishlist
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.