Complemented by three other documents: ../CHANGELOG.md, KnownIssues.md, and BreakingChanges.md. Where the Changelog is a terse, itemized record of what changed, this document is the narrative version — the highlights worth reading before upgrading.
2.0.0 was a significant rewrite of the original extension in order to add a test suite, address open issues, and more easily support future fixes and features.
This release also replaces the extension’s dependency on the third-party Test Explorer UI extension with Visual Studio Code’s own native Testing API. The Testing view, gutter run/debug icons, and inline failure messages are now provided directly by VS Code — hbenl.vscode-test-explorer is no longer required and may be uninstalled if you do not use it elsewhere.
Debugging a test is also more reliable. The extension now resolves the test executable’s path itself before starting the debug session, rather than relying on a VS Code command being resolved at an unpredictable time, fixing the “wrong executable path” / “No debug test executable found” class of bugs.
See BreakingChanges.md for the full detail on the Test Explorer UI migration — in short, if your settings.json or workflow assumed the third-party Test Explorer view, you'll now use VS Code’s built-in Testing view instead.