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
Given the below tests, when I run m /spec.rb:8, I expect the m runner to only execute the test in scenario2. But instead, it executes both scenario1 and scenario2 because the two "it" sections have the same description.
1describe'scenario1'do2it'is a good test'do3 ...
4end5end67describe'scenario2'do8it'is a good test'do9 ...
10end11end
The text was updated successfully, but these errors were encountered:
@gi Yeah I wanted functionality more like rspec's line number test selection. Rspec tests are a lot easier to run than minitest in my vim test runner because it's easy for vim to reference the line number instead of trying to parse the "it" description string.
I was hoping m would help me get minitest working automagically with my vim test runner since it enables line number selection. m does help get things going but I found this error with two matching "it" clauses in different describe sections. It doesn't seem like m is meant to run both tests.
Given the below tests, when I run
m /spec.rb:8
, I expect them
runner to only execute the test in scenario2. But instead, it executes both scenario1 and scenario2 because the two "it" sections have the same description.The text was updated successfully, but these errors were encountered: