Skip to content
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

Numbered list of failed specs #3078

Open
loqimean opened this issue Apr 16, 2024 · 2 comments
Open

Numbered list of failed specs #3078

loqimean opened this issue Apr 16, 2024 · 2 comments

Comments

@loqimean
Copy link

Subject of the issue

It would be fine to have numbered list of specs, like wew have them numbered in a detailed view, but then, in the bottom, we just see list. So, when I see detailed spec with a number for example 4 and would like to run it, I'm going to bottom and I must to search where is that spec by manual numbering. So, adding numbers there too would be nice, isn't?

Your environment

  • Ruby version: any (even 3.x)
  • rspec-core version: any (even 3.x)

Steps to reproduce

Just fails more than one test

Expected behavior

We see failed specs when them are described, like this:
Screenshot 2024-04-16 at 11 06 20
And then in the bottom we see also numbered list here:
Screenshot 2024-04-16 at 11 07 04

Actual behavior

We see numbers for detailed specs only and when we going to bottom to copy a path for such spec it requires to find it by myself

@loqimean
Copy link
Author

This improvement adds +100 to speed of debugging failed specs. I can open PR for this if it's really relevant

@JonRowe
Copy link
Member

JonRowe commented Apr 20, 2024

👋 If you wanted to add the failure number to the comment, that seems reasonable, but note it has to be in the comment because those lines are designed to be directly copy / pastable into a shell... You could also easily produce a custom formatter to do this yourself in a gem etc

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

No branches or pull requests

2 participants