You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
And then in the bottom we see also numbered list here:
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
The text was updated successfully, but these errors were encountered:
👋 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
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
Steps to reproduce
Just fails more than one test
Expected behavior
We see failed specs when them are described, like this:
And then in the bottom we see also numbered list here:
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
The text was updated successfully, but these errors were encountered: