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
Testing enhancement: Testing individual rules or cases #501
Comments
Yes, that would indeed be useful. |
I have something working locally as a patched version of However, as I see no good way to get ava to dynamically ignore a test after the tests have begun, I see no way to avoid getting messages for each ignored file such as "No tests found in test/prefer-trim-start-end.js". I suppose we could instead dynamically build a CLI glob pattern but besides feeling hacky and requiring some significant changes to the existing test files, this would not become available by default to all |
I have a VSCode configuration to run/debug an individual test file that I can share if that would be helpful. |
@jmoore914 You wouldn't happen to have that VSCode config still lying around would you? |
@travismorenz I don't, I'm sorry! |
For
eslint-plugin-jsdoc
, we have added a convenient testing feature that allows us to run tests likenpm run test-index --rule=xyz --invalid=3-5
ornpm run test-index --rule=xyz --valid=-1
(with slice-like ranges/indexes/negative indexes). This alone has been extremely helpful for rapid testing and development, and I would suggest it be considered foreslint-plugin-unicorn
.Alternatively, or in addition, one might add
only: true
oronly: 1
to a given tests to behave like Mocha'sit.only
, changing the default to run no tests except those with anonly
property.The text was updated successfully, but these errors were encountered: