-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Add docs for tpv0 removal #48173
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
base: main
Are you sure you want to change the base?
Add docs for tpv0 removal #48173
Conversation
|
Adding @gewarren as a reviewer as this is related to breaking changes in the product. |
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds documentation to help users migrate away from the legacy test runner (TPv0/TMI) that was removed in VSTest 18.0.0. The documentation provides guidance for resolving errors encountered when upgrading and directs users to appropriate migration paths.
Key changes:
- Creates a new migration guide for users encountering TPv0 removal errors
- Adds navigation entry to make the guide discoverable in the testing documentation
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| docs/core/testing/unit-testing-mstest-migration-from-tmi.md | New migration guide explaining TPv0 removal and providing solutions for common scenarios |
| docs/navigate/devops-testing/toc.yml | Adds navigation entry for the new migration guide in the testing documentation table of contents |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Head branch was pushed to by a user without write access
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Summary
Adds short doc that is linked from the error shown when tpv0 is used in VSTest 18. The component was removed and this doc will help dispatching the users to migration documents, especially mstest v1 to mstest v3 where we expect the most "traffic". This is also a place that we can update with additional FAQ etc as more people encounter this error.
Internal previews