Opened 9 years ago

#6364 enhancement new

page trial summary output

Reported by: Jean-Paul Calderone Owned by:
Priority: normal Milestone:
Component: trial Keywords:
Cc: Jonathan Lange Branch:
Author:

Description

With enough failures or errors, trial's summary output can be quite long. When fixing such cases, it is sometimes inconvenient to find the top of the current run's summary output. It can be easy to confuse a previous run's results with the most recent run's results (particularly for people new to test driven development or new to using trial in particular).

Sending the summary output to a pager would probably address this usability issue. This would make the user's experience interpreting the output of a particular run interactive and would make it much easier to ignore any previous run's output.

There are probably other ways to achieve these desirable attributes, so the solution might not be to do the simple (ha), obvious thing of launching $PAGER and sending trial's output through it - or even implementing our own paging logic. But these are solutions that seem most obvious.

Clearly this should not be done if there is no user looking at the results - in other words, if output is not a PTY then the current behavior is probably better. Perhaps it should not even be the behavior of the default runner, although I suspect it would provide a better user experience than the default runner in most cases.

Change History (1)

comment:1 Changed 9 years ago by DefaultCC Plugin

Cc: Jonathan Lange added
Note: See TracTickets for help on using tickets.