Standardize ANSI markup on all terminal output sections
See original GitHub issueCurrently (7.2.0.dev264+g6ad32a9c5), the console heading for some sections is colorized (‘warnings’, ‘short test summary info’); while other sections are not (ERRORS, FAILURES, PASSES, and ‘rerun test summary info’ if the pytest-rerunfailures plugin is installed). Also, the ‘test session starts’ and ‘short test summary info’ sections are in bold, while none of the others are.
Enhancement request is to standardize ANSI markup for the various sections. If it were up to me, I would simply add colors to the section headings that are not colored: PASSES (green), FAILURES (red), ERRORS (yellow).
Issue Analytics
- State:
- Created a year ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
ANSI escape code - Wikipedia
ANSI escape sequences are a standard for in-band signaling to control cursor location, color, font styling, and other options on video text terminals...
Read more >List of ANSI color escape sequences - terminal - Stack Overflow
I'm looking for a list of all supported colors and options (like bright and blinking). As there are probably differences between the terminals...
Read more >Build your own Command Line with ANSI escape codes
This post will explore the basics of how you can control the terminal from any command-line program, with examples in Python, and how...
Read more >ANSI Standard (X3.64) Control Sequences for Video ...
Many computer terminals and terminal emulators support color and cursor control through a system of escape sequences. One such standard is commonly referred...
Read more >Is there any manual page for colored shell output?
Even with apropos color or something similar. So, the question is - where I can find reliable manuals? terminal · colors · documentation....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@doublevcodes - if you would like help reproducing the above issue (i.e. if you want to run those tests), let me know. They are basically taken from https://github.com/jeffwright13/pytest-tui/tree/main/demo-tests.
It should be largely contained in the terminalwriter
It’s likely some preparing cleanup is necessarily
It would be nice if we could prepare the code for eventual direct integration of stuff like the ide plugins for testing and pytest-TUI
Terminalwriter has a lot of painful legacy