subunit reporter should include time information
Open
Nobody has claimed this yet.
enhancement
new
priority-low
trial
- Dominant language
- Python
- Stars
- 6k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Description
 |
@jml reported |
|---|---|
| Trac ID | trac#4716 |
| Type | enhancement |
| Created | 2010-10-26 14:20:11Z |
trial --reporter=subunit twisted.trial outputs correct subunit output, but does not include time: events in the stream, which makes it difficult to analyze how much time is spent on tests.
Since subunit output is intended for machine reading, clutter is not a factor.
Searchable metadata
trac-id__4716 4716
type__enhancement enhancement
reporter__jml jml
priority__low low
milestone__
branch__
branch_author__
status__new new
resolution__None None
component__trial trial
keywords__
time__1288102811000000 1288102811000000
changetime__1295808879000000 1295808879000000
version__None None
owner__
cc__therve
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the trial --reporter=subunit twisted.trial command and trace how its stream output is produced. Confirm how time: events are represented in subunit, then make the reporter include timing information so the machine-readable stream supports test-duration analysis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100