-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
feat: implement forc-test
filter
#4566
Conversation
forc-test
filter
Thanks for the quick turnaround on this! From the LSP perspective, it would be nice to have a way to exact match on a test name. I would use this for the runnable button (which runs an individual test). Without exact matching, there would be no way to make it run only the 1. An Feel free to make a separate issue for this if it's out of scope. |
c1faec7
to
9c57fa9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, mostly nits 👍
5e408ec
to
719ac9d
Compare
Thanks for the review @sdankel, should be good to go! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One tiny optional change but otherwise utACK
Description
closes #3268.
This PR adds filtering capability to
forc-test
based on test names. Tests are executed if their name contains the given filter phrase.Checklist
Breaking*
orNew Feature
labels where relevant.