search

JohnnyHendriks / TestAdapter_Catch2

Visual Studio Test Adapter for Catch2
MIT License
104 stars 29 forks source link

"Tests not found" #35

Closed enkeyz closed 3 years ago

enkeyz commented 4 years ago

So I got this message after I run the tests.

[2019. 12. 06. 6:46:01.428 du.] ---------- Discovery started ---------- Test Adapter for Google Test: Test discovery starting... Test discovery completed, overall duration: 00:00:00.0418552 Started Catch2Adapter test discovery... Finished Catch2Adapter test discovery. No test is available in C:\Users\enkeyz\source\repos\chapter10\x64\Debug\Listing10-1.exe. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again. [2019. 12. 06. 6:46:02.132 du.] ========== Discovery finished: 0 tests found (0:00:00,6366892) ========== No tests found to run. No tests found to run.

ScottHutchinson commented 4 years ago

Note "Test Adapter for Google Test"

Try disabling Google Test and other test adapters than Catch2.

enkeyz commented 4 years ago

Same message. Disabled both Google and Boost Test adapters.

[2019. 12. 06. 8:05:27.570 du.] ---------- Discovery started ---------- Started Catch2Adapter test discovery... Finished Catch2Adapter test discovery. No test is available in C:\Users\enkeyz\source\repos\chapter10\x64\Debug\Listing10-1.exe. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again. [2019. 12. 06. 8:05:28.272 du.] ========== Discovery finished: 0 tests found (0:00:00,7003098) ==========

I'm using latest VStudio 2019 with ReferenceTests.runsettings(also tried with the minimal).

Tests are working tho: https://i.imgur.com/Oaj7WJz.png just not with the adapter.

ScottHutchinson commented 4 years ago

Yeah, I've never been able to get this adapter to work with our projects in VS 2017. There are a few open issues regarding test discovery, which might have information that will help you.

JohnnyHendriks commented 4 years ago

To diagnose a little further what is going on you can do the following. Set logging to debug (i.e., add the following setting to the runsettings-file

<Logging>debug</Logging>

Note, with VS2019 you may need to switch configurations (e.g., from Debug to Release) and build the test between discovery actions otherwise VS2019 may think it does not need to discover as it may assume it has the tests in the cache.

Also, you could run the executable on the commandline with the following parameters

Listing10-1.exe --verbosity high --list-tests *

This is the default command line used by the test adapter when discovering tests.

MPJansen commented 4 years ago

Having a similar problem, the reference project detects the testcases but will not run them. Might there be something similar going on to this?

Thanks for your effort though!

JohnnyHendriks commented 3 years ago

Just released a new version (1.6.0) and cleaning up issues now. I do not know if there is anything more I can do with this, so closing the issue.

But just to add a little extra info (not related to the original issue). I've noticed that when switching configuration, and trying to run a test without re-building first, it will not run the test. It probably gets confused between the executables for the different configurations.