Skip to content
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.

Sign up for GitHub

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

Convert header to warnings #866

Merged
merged 3 commits into from
Dec 5, 2023
+14 −14
Merged

Convert header to warnings #866

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
70192eb
Convert to warnings
SeanKilleen Dec 5, 2023
7a6a644
More
SeanKilleen Dec 5, 2023
f88f302
More
SeanKilleen Dec 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 12 additions & 14 deletions docs/articles/vs-test-adapter/Adapter-Engine-Compatibility.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,17 +40,15 @@ table above.
Note that most of what the console can do, can be done using the `dotnet test` command with the appropriate runsettings
added, see [Tips&Tricks](https://docs.nunit.org/articles/vs-test-adapter/Tips-And-Tricks.html).

## :warning: Warning

If you try to add another engine version package, it may seem that the adapter and test are still working. That is just
by luck, and it does so because the interfaces between the version you have added are the same as the embedded version.
But if you try to use a feature that is not in the embedded version, it will fail.

Most likely you will see messages about "no tests found", or it may simply crash during test.

## :warning: Warning

Version 4.4.1 use an engine version that is not released yet. This is because the engine has a bug that prevents it
from working with the adapter. The bug is fixed in the engine, but the fix is not yet released. The adapter will be
updated to use the released engine version as soon as it is released. You may try to use 3.15.2, but we can currently
not confirm that it works.
> [!WARNING]
> If you try to add another engine version package, it may seem that the adapter and test are still working. That is just
> by luck, and it does so because the interfaces between the version you have added are the same as the embedded version.
> But if you try to use a feature that is not in the embedded version, it will fail.
>
> Most likely you will see messages about "no tests found", or it may simply crash during test.
<!-markdownlint-disable MD028-->
> [!WARNING]
> Version 4.4.1 use an engine version that is not released yet. This is because the engine has a bug that prevents it
> from working with the adapter. The bug is fixed in the engine, but the fix is not yet released. The adapter will be
> updated to use the released engine version as soon as it is released. You may try to use 3.15.2, but we can currently
> not confirm that it works.