-
Notifications
You must be signed in to change notification settings - Fork 451
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 tests for templates #47
Comments
@DamianEdwards we have some tests now, how would you describe the gap (or should we close this now) |
Happy for engineering to decide as I haven't looked at the tests added. If we have basic coverage now of project create, build, run, publish from all our templates we can close and open specific issues to add missing coverage when necessary. |
@radical has been working on the infrastructure to support these types of tests. I believe he is close to getting those changes in, but IMO this is not something that should be blocking the release and the change will likely not be backported given the timing now, So I'm moving the milestone to 8.1. |
This adds `Aspire.Workload.Tests` which are meant to exercise the `aspire` workload. The individual tests create projects from templates just like a user would, and then run, and validate them. It uses the existing infrastructure from `Aspire.EndToEnd.Tests` to install sdk+workload for testing. - Enables tests on Linux, and Windows - Because we don't have docker support on helix/Windows yet, the docker dependent tests are skipped on windows ## Tests Two kinds of tests are being added here: 1. Tests that create+build a `aspire-starter` template project, and then some tests interact with that running app to validate it 2. Individual tests exercise the various templates, for example to create `aspire-starter` with [xunit,nunit,mstest] options - The tests also connect to the dashboard and validate that the expected services show up as expected using `Playwright`. - Some tests also connect to the webapp in `aspire-starter` template to validate some parts of it. Fixes #47 . Follow up work is tracked in #4222 Co-authored-by: Eric Erhardt <eric.erhardt@microsoft.com> Co-authored-by: Jose Perez Rodriguez <joperezr@microsoft.com>
The templates currently have no unit test coverage. We should look at porting some of the template testing infrastructure from dotnet/aspnetcore to enable us to get some template test coverage.
The text was updated successfully, but these errors were encountered: