-
Notifications
You must be signed in to change notification settings - Fork 379
Add common arcade test targets #1704
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
Conversation
|
So with this change if I want to generate helix archives from a build script i.e for CI or official builds, I have to do |
|
I don't have a strong opinion on that. The reason why chose this is that ArchiveTests handles the ArchiveTests target and GenerateTestScripts handles the GenerateRunScript target. I think it's a good idea to bundle it together :) |
|
LOL actually I just saw that |
|
So then GenerateTestScript target will be hooked together by the dependent targets 😄 that is a nicer approach. |
|
@safern ready to merge? |
bb7295b to
6fd6013
Compare
|
@safern @ercistj PTAL. I think this is now ready to be merged. |
|
|
||
| <Target Name="GenerateRunScript" | ||
| Inputs="unused" | ||
| Outputs="$(RunScriptOutputPath)" |
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.
Why inputs outputs if you don't use them for incremental nor batching?
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.
GenerateRunScript is part of the incremental build, at least that's what I believed.
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.
I meant that if you have no inputs and only outputs I would expect that target to always run.
| still generates the test execution script and archives the test dir for Helix consumption. | ||
| --> | ||
| <Target Name="RunTests" | ||
| Condition="'$(SkipTests)' != 'true' OR '$(TestDisabled)' == 'true'" |
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.
Interesting that this was inverted before. No-one was using it?
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.
Yeah I freaked out when I saw that condition 🤐
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.
No idea, but will follow-up on that one.
safern
left a comment
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.
LGTM
Relates to dotnet/corefx#34385
Changes:
/p:ArchiveTests=Tests|IntegrationTests|PerformanceTests|(Packages)|All.$(SkipTests)property which is not needed anymore as the test targets should only be used if you REALLY want to run tests.$(Performance)property which is not needed anymore as performance tests now have a unique target and performance related msbuild files are only imported if `IsPerformanceTestProject´ equals true./t:Test,/t:IntegrationTestand/t:PerformanceTest. These are the common arcade targets that are expected to be present in the respective test project type.