[dotnet-watch] E2E tests for dotnet-watch

[javiercn]

It's not clear to me why we don't have a suite of E2E tests for dotnet-watch, especially since many of the behaviors are OS specific.

There are a host of things we could test in an automated fashion instead of relying on manual testing, which would help us detect issues faster and prevent regressions.

The general flow for an E2E dotnet watch test would be something like:

• Create/Use an existing project.
• Run dotnet watch
• Capture the state for the site/page with something like Selenium/Playwright.
• Make some change to the files programatically (essentially copy/paste new content into the file)
• Watch (no pun intended) the tool react to the changes.
• Check the after state on the site to validate the changes were correctly applied.
• Capture a bunch of info otherwise (logs, browser, etc) to figure out what went wrong.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.