The MSBuild project property group element <IsTestProject> (for instance set to true when creating a test project with xUnit) seems ignored by Ionide. So having <IsTestProject>false</IsTestProject> does not remove the project from the test explorer and a Ionide warning about missing tests pops up when there are not tests in the projects.
The predicate ProjectExt.isTestProject checks if "Microsoft.TestPlatform.TestHost" or "Microsoft.NET.Test.Sdk" are in the project’s package references. But in the example repository mentioned below, a single set of paket packages is shared between projects.
Would it be possible to check something related to IsTestProject that would be higher priority?
Steps to reproduce
Add <IsTestProject>false</IsTestProject> in a project property group of a MSBuild project file and the project will still appear in the test explorer.
Link to sample reproduction
In the https://github.com/laurentpayot/fsharp-fable-elmish-example repository, the app.fsproj project file has <IsTestProject>false</IsTestProject> but it appears in the list of test projects and a Ionide warning about missing tests pops up.
Expected behaviour
Having <IsTestProject>false</IsTestProject> should remove the project from the test explorer projects and we should see no Ionide warning about missing tests in that project.
Describe the bug
The MSBuild project property group element
<IsTestProject>
(for instance set totrue
when creating a test project with xUnit) seems ignored by Ionide. So having<IsTestProject>false</IsTestProject>
does not remove the project from the test explorer and a Ionide warning about missing tests pops up when there are not tests in the projects.The predicate
ProjectExt.isTestProject
checks if "Microsoft.TestPlatform.TestHost" or "Microsoft.NET.Test.Sdk" are in the project’s package references. But in the example repository mentioned below, a single set of paket packages is shared between projects. Would it be possible to check something related toIsTestProject
that would be higher priority?Steps to reproduce
Add
<IsTestProject>false</IsTestProject>
in a project property group of a MSBuild project file and the project will still appear in the test explorer.Link to sample reproduction
In the https://github.com/laurentpayot/fsharp-fable-elmish-example repository, the app.fsproj project file has
<IsTestProject>false</IsTestProject>
but it appears in the list of test projects and a Ionide warning about missing tests pops up.Expected behaviour
Having
<IsTestProject>false</IsTestProject>
should remove the project from the test explorer projects and we should see no Ionide warning about missing tests in that project.Machine info