We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Minor issue but it caused me a headache to pin down and see what was happening.
I have two test files with the same suite name:
//MyComponent.test.js describe("MyComponent", function().... //MyComponent.test.jsx describe("MyComponent", function()....
After putting a .only on the first suite, it was running tests in the second one:
.only
//MyComponent.test.js describe.only("MyComponent", function().... //THESE TESTS RUN INSTEAD! //MyComponent.test.jsx describe("MyComponent", function()....
The obvious fix was to change the suite titles so they are unique, but I feel like this should either be fixed or well documented somewhere.
The text was updated successfully, but these errors were encountered:
+1
Just encountered the same
Sorry, something went wrong.
let's just say only doesn't work the way you think it does (it uses pattern matching). this has been addressed in many issues already
only
No branches or pull requests
Minor issue but it caused me a headache to pin down and see what was happening.
I have two test files with the same suite name:
After putting a
.only
on the first suite, it was running tests in the second one:The obvious fix was to change the suite titles so they are unique, but I feel like this should either be fixed or well documented somewhere.
The text was updated successfully, but these errors were encountered: