microsoft / microsoft/aspire-samples
Start thinking about leveraging aspire-samples existing tests as part of our overall test coverage
Open
@DamianEdwards is already working on this.
Since May 24, 2024.
area-engineering-systems
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 345
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 30
Description
As discussed offline, we should begin to think about how to use aspire-samples and their tests as part of our overall testing story in Aspire. This includes the following:
- Enabling a daily run which updates the version of aspire used by the samples and ensure that the projects still compile, as well as ensuring that they can run their tests successfully.
- Ensuring we have some gates to detect any breaking changes needed when trying to upgrade from version to version. Ideally, we'd like to validate that updating from a stable version to the nightly version would be possible in a non-breaking way.
Assigning @DamianEdwards for now as he has started to do some thinking here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.