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
I have an integration test file with three tests in it. The first has 4 assertions, the second 10, and the third 1. If I place the caret in the first test and use Command-Shift-R to run the test, it works perfectly: 4 assertions and it shows the title of the first test at the top of the output. If I place the caret inside the second test and use Command-Shift-R, it runs the first test again: 4 assertions and the title of the first (not second) test. Finally, if I do the same thing with the caret in the third test, it runs as expected, showing 1 assertion and the name of the third test above the output.
The text was updated successfully, but these errors were encountered:
I am using Sublime Text 3 and minitest, and having the same issue. If I move the broken test to be the first one in the file, put my cursor in the test and run cmd+shift+r, it says "No test name!".
I appeared to have fixed the issue by removing the first line of my test which includes the name, and retyping the line. I was also able to move the test after this.
Still does this for me. I should note that I am able to fix the issue by NOT using symbols in the test name. In my case, I was using a > symbol, removing that makes the test run with no problems.
I have an integration test file with three tests in it. The first has 4 assertions, the second 10, and the third 1. If I place the caret in the first test and use Command-Shift-R to run the test, it works perfectly: 4 assertions and it shows the title of the first test at the top of the output. If I place the caret inside the second test and use Command-Shift-R, it runs the first test again: 4 assertions and the title of the first (not second) test. Finally, if I do the same thing with the caret in the third test, it runs as expected, showing 1 assertion and the name of the third test above the output.
The text was updated successfully, but these errors were encountered: