Repository navigation
Integration Tests Should be Updated after .NET preview1 and GA Releases #665
Description
See #657
After a preview1 or GA release of a major .NET version, the integration tests in this repo should be updated to reflect changes and ensure compatibility. We should decide on a tracking system or process (issue labels, checklist, documentation, etc.) for this work.
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
- Status
Activity
[-]Integration Tests Should be Updated after preview1 and GA .NET Releases[/-][+]Integration Tests Should be Updated after .NET preview1 and GA Releases[/+]ellahathaway commentedon Nov 19, 2025
[Triage] We should be on top of updating the tests which correlate with preview releases starting with preview1. For
qualityintegration tests such as https://github.com/dotnet/install-scripts/pull/657/files#diff-f8f7a4822332fe9139ae369134d72cd9a4f0e652d025bc4730ba68db77332169R41-R43, we should make those updates starting with RC1.For these updates, we should create an issue template (either in this repo or the releases repo) that describes the work needed to update the integration tests. In these templates, we should consider adding a copilot prompt so that we can assign copilot to these issues. Additionally, we should update the monitoring dashboard to note when to create these issues.
Add Copilot agent skill for updating integration tests after .NET rel…
Add Copilot agent skill for updating integration tests after .NET rel…
Add Copilot agent skill for updating integration tests after .NET rel…