-
Notifications
You must be signed in to change notification settings - Fork 676
Add "group" metadata to define which tests will be run #2527
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
Comments
This is a much needed feature. Ability to run a particular category of tests using their meta data set on the test or the fixture. Testcafe version : 0.21.1 |
Is there any way to use the filter when a test omits the meta tag. ie |
@jafin As the docs state: metadata value's are strings, so it really doesn't have sense to speak of truthy or falsy value. If you read the PR's comments, you will fully understand the cmd line api decision. Anyway, you can implement you own custom runner, using the programming interface, to have the custom behavior that you need. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs or feature requests. For TestCafe API, usage and configuration inquiries, we recommend asking them on StackOverflow. |
…ress#2954) * Updated filter docs. closes DevExpress#2527 * Updated filter cli docs. closes DevExpress#2527 * updated doc * fix lint
Are you requesting a feature or reporting a bug?
A feature, posted by one of TestCafe customers (see details below)
In one of the recent releases I noticed that test and fixture metadata can now be added to the test scripts. Would it be possible in the future to use the metadata of a test to group them when running from command line? ie setting test.meta({sanity: true, fullRegression: true, feature1: false}) then from command line start all tests that have --meta '{sanity: true}' when i want to run only a small subset of my scripts?
I'm currently doing this using globs on Fixture and Test names but they will become long and involved with too many unsafe keywords when I expand my test suite.
Specify your
The text was updated successfully, but these errors were encountered: