Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Initial support of Microsoft.Testing.Platform #1153
Initial support of Microsoft.Testing.Platform #1153
Changes from 1 commit
d7dc497
9da8cd9
24133f3
49326bd
3789fff
8754cd1
c3fa697
8970bc7
b588819
e742849
9a340ce
23c6da7
80da537
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Some equivalent to the "TestContainer" capability for the new platform.
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.
Register the hook called by
Microsoft.Testing.Platform.MSBuild
when auto-generating the entry point.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.
Moved to the target, see there for explanation.
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.
The first line enables/disables the generation of the entry point for the new platform and the second line disables the VSTest entry point if the new platform is enabled.
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.
Is it necessary to disable the VSTest entry point?
It would be better if the user decides without having to use any parameters. If he runs it using
dotnet test
, it would use that entry point, if he runs the executable, it would use that entry point.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.
VSTest always creates its own entry point. Our new platform also wants to auto-generate it (to simplify user experience) so we need to have them mutually exclusive.
Not really, as you could see in the example because
dotnet test
is pretty common gesture, we have a mode to hook into it skipping VSTest redirection and calling the runner instead.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.
With the current layout, the adapter now needs to be added as a reference as it contains the
AddNUnit
extension point used by the hook. It's definitely possible to produce a different dll if you prefer.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.
The bridge as a deps on object model (Microsoft.TestPlatform.ObjectModel >= 17.5.0). If that's a too big constraint for you, we need to do some manual tests here to see if we would break something when doing a forced downgrade here.
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.
We have been running on the old 11.0 for net framework, and with 15.0.0 for .net.
I would assume that 17.5 would limit this to VS 2022, and the question then is if we should add another target. That is something we could do, to keep backwards compatibility a bit longer.