-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Host tests should move out of the build and use the libraries test infrastructure #94271
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsToday host tests run on the build machine inside the build itself. This causes problems - test failures are build failures, they only run on the configurations we happen to build on, etc. We need to move those tests out of the build. Since they are written as plain old xunit tests they should be able leverage the libraries test infrastructure.
|
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsToday host tests run on the build machine inside the build itself. This causes problems - test failures are build failures, they only run on the configurations we happen to build on, etc. We need to move those tests out of the build. Since they are written as plain old xunit tests they should be able leverage the libraries test infrastructure.
|
@elinor-fung has been working towards that for a while - we need to cleanup how the tests get their "Assets" first. |
This is the list I wrote up awhile back for what I think needed to happen: |
I would go as far as saying "they should leverage the Arcade common test infrastructure". The libraries test infrastructure is more complex and Arcade should already offer everything needed. AFAIK the host tests already use the VSTest runner and submitting to helix is fairly trivial with the Helix Sdk. |
I'm going to close this as a dup of #77800, as I think that covers everything we need |
Today host tests run on the build machine inside the build itself. This causes problems - test failures are build failures, they only run on the configurations we happen to build on, etc.
We need to move those tests out of the build. Since they are written as plain old xunit tests they should be able leverage the libraries test infrastructure.
The text was updated successfully, but these errors were encountered: