Skip to content

Custom tasty consoleReporter #4592

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fendor opened this issue May 13, 2025 · 0 comments
Open

Custom tasty consoleReporter #4592

fendor opened this issue May 13, 2025 · 0 comments
Labels

Comments

@fendor
Copy link
Collaborator

fendor commented May 13, 2025

There are two issues with the current consoleReporter (which are both mostly nitpicks and my personal preference).

  1. It can be hard to find the test case that was failing during a test run (especially on CI)
  2. The alignment of the test output can be sometimes hard to read (see Use shorter test names in ghcide-tests #4591 where this caused an issue for me)

I am proposing that we introduce a custom consoleReporter which fixes both of these "shortcomings".
I have a prototype that makes the output look like this:

Image

This makes the output more terse, but not necessarily easier to read. It is only easier to read, if the test names are too long, like in #4591, which can be generally worked around (by using shorter test names).

Additionally, I would propose a succinct summary at the end of the test execution if the test failed, which should fix my first issue with the consoleReporter.
If we had a custom consoleReporter, this would be relatively easy to add.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant