-
Notifications
You must be signed in to change notification settings - Fork 207
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
Add -category argument to TestRunner #5358
Conversation
Looks like in this test, turning off the release build performance tests took 700 seconds vs 1300 seconds. I'm not sure whether that means it's worth it to turn them off |
I guess it depends on what we're trying to optimise - time to first green check, or time to all green checks. If it's all green checks then we might as well keep running the performance tests on release builds, because they'll still be finishing faster than the linux debug build (although we might want to drop them from windows?). If it's time to first green check then it might be worth dropping. I think I'd be inclined to keep, at least on Linux. |
4dd9fdf
to
7d5c3a0
Compare
This builds on the work done in GafferHQ#5358, allowing tests to be assigned to arbitrary categories using a new `CategorisedTestMethod` decorator. It also offers improved filtering by category in `gaffer test` by supporting wildcards and adding a `-excludedCategories` argument. This will allow us to use test categories to group tests that are related in some way and are commonly run together during development.
This builds on the work done in GafferHQ#5358, allowing tests to be assigned to arbitrary categories using a new `CategorisedTestMethod` decorator. It also offers improved filtering by category in `gaffer test` by supporting wildcards and adding a `-excludedCategories` argument. This will allow us to use test categories to group tests that are related in some way and are commonly run together during development.
This builds on the work done in GafferHQ#5358, allowing tests to be assigned to arbitrary categories using a new `CategorisedTestMethod` decorator. It also offers improved filtering by category in `gaffer test` by supporting wildcards and adding a `-excludedCategories` argument. This will allow us to use test categories to group tests that are related in some way and are commonly run together during development.
This builds on the work done in GafferHQ#5358, allowing tests to be assigned to arbitrary categories using a new `CategorisedTestMethod` decorator. It also offers improved filtering by category in `gaffer test` by supporting wildcards and adding a `-excludedCategories` argument. This will allow us to use test categories to group tests that are related in some way and are commonly run together during development.
This builds on the work done in GafferHQ#5358, allowing tests to be assigned to arbitrary categories using a new `CategorisedTestMethod` decorator. It also offers improved filtering by category in `gaffer test` by supporting wildcards and adding a `-excludedCategories` argument. This will allow us to use test categories to group tests that are related in some way and are commonly run together during development.
This builds on the work done in GafferHQ#5358, allowing tests to be assigned to arbitrary categories using a new `CategorisedTestMethod` decorator. It also offers improved filtering by category in `gaffer test` by supporting wildcards and adding a `-excludedCategories` argument. This will allow us to use test categories to group tests that are related in some way and are commonly run together during development.
This builds on the work done in GafferHQ#5358, allowing tests to be assigned to arbitrary categories using a new `CategorisedTestMethod` decorator. It also offers improved filtering by category in `gaffer test` by supporting wildcards and adding a `-excludedCategories` argument. This will allow us to use test categories to group tests that are related in some way and are commonly run together during development.
As discussed, replace -performanceOnly with a more flexible argument.
Since we haven't decided yet whether to set release builds to
-category standard
, I tried setting up a temp build with it set for comparison purposes ... we'll see if I botched that syntax.