-
Notifications
You must be signed in to change notification settings - Fork 132
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
.NET 8: Design E2E testing solution for source-build/VMR #3015
Comments
@richaverma1 Is this something you might be interested in helping work on for .NET 8? |
I view support for running in an offline mode part of this work. |
Linking to the scenario testing design document - https://github.com/dotnet/arcade/blob/main/Documentation/UnifiedBuild/Scenario-Testing.md @mmitche - what design work remains for this issue? |
@mmitche - Can this be closed? What work remains? TIA |
Describe the Problem
.NET does not currently have a unified set of automated scenario tests that are run against the product. We do have testing provided by vendors, we do have a wide variety of unit tests run against product repositories, and we do have SDK tests the closely mimic the product. However, we are missing general scenario tests.
This is not great for the source-built Linux product. Aside from a series of smoke tests, partners do not have a great way to verify that what they build meets a quality bar. The unit tests that are also present in the product repos do not generally work against the end product, and often require resources that our partners are not able to use in their testing environments.
Describe the Solution
.NET should have a series of automated scenario tests that can run against the end product. These scenario tests and their infrastructure should be designed in such a way that:
This issue covers three aspects:
The text was updated successfully, but these errors were encountered: