You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that test-case discoverability depends on the case of the filename as referenced in the Solution file. Other test runners (e.g. GTest) do not fail on this.
If the case of the filename and the name of the project does not match, the discovery will fail and give an "Invalid source" error, e.g:
After some digging it turned out that the following line in my solution file was the culprit:
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "CoreTests", "coretests\coretests.vcxproj", "{BEC24047-EEE1-EE48-DAA5-85524471212A}"
After changing it to match the case of the project name it worked:
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "CoreTests", "coretests\CoreTests.vcxproj", "{BEC24047-EEE1-EE48-DAA5-85524471212A}"
Not entirely sure if this is an issue with the VS test runner or with the adapter, but even if it's in VS, perhaps this is something that could be worked around in the adapter.
The text was updated successfully, but these errors were encountered:
It seems that test-case discoverability depends on the case of the filename as referenced in the Solution file. Other test runners (e.g. GTest) do not fail on this.
If the case of the filename and the name of the project does not match, the discovery will fail and give an "Invalid source" error, e.g:
CheckSource name: coretests
Invalid source.
Accumulated Testcase count: 0
After some digging it turned out that the following line in my solution file was the culprit:
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "CoreTests", "coretests\coretests.vcxproj", "{BEC24047-EEE1-EE48-DAA5-85524471212A}"
After changing it to match the case of the project name it worked:
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "CoreTests", "coretests\CoreTests.vcxproj", "{BEC24047-EEE1-EE48-DAA5-85524471212A}"
Not entirely sure if this is an issue with the VS test runner or with the adapter, but even if it's in VS, perhaps this is something that could be worked around in the adapter.
The text was updated successfully, but these errors were encountered: