Frequently Asked Questions

Frequently Asked Questions

• I am getting: error MSB4018: The "VCMessage" task failed unexpectedly.

  • This issue is most probably due to a missing project property. Open the project properties window and from the General section, set the Platform Toolset to an appropriate value of choice.

• My tests are not being discovered

  • If the test adapter logs in the 'Test' section of the output pane do not list the test module, chances are that Visual Studio is not considering the module. This has been a known issue (Issue #167) with Visual Studio 2015 Update 2 and Update 3 in cases where the test module is located within a path which contains the '#' symbol.
  • The test adapter tries to launch your test module in order to discover your tests. If your module fails to start (e.g. because it depends on DLLs which are not in your PATH), an error will be logged in the 'Test' section of the output pane. If you see such an error, try running your test module outside the adapter in order to analyse the issue.
  • Based on the discovery method chosen (either automatically or based on configuration), certain tests will not be discovered. In addition, based on how Boost.Test is compiled within your test module (compiled as part of the module or used via the shared library), will also affect test discovery. Consider using test filtering and setting the <ForceBoostVersion> configuration element to aid in test discovery. Refer to the Configuration section for further information.

• My tests are failing after updating to v1.0.7.X

  • In v1.0.7.X, the adapter is now 'working directory' aware - previous versions assumed the working directory as the directory in which the test module is located (i.e. $(TargetDir)). The test module is now launched based on the working directory defined in the Visual Studio debugging property page (which defaults to $(ProjectDir)) or as expressed in the <WorkingDirectory> configuration option.

• All my tests are failing with the error message Boost Test result file was not found or is empty. when using Boost.Test released with Boost 1.62

  • If you are compiling your module with Boost.Test released with Boost 1.62, the test runner will fail to accept the command line arguments --log_sink and --report_sink. In order to remedy this, a workaround is available and can be enabled via .runsettings configuration. Refer to the Configuration section for further information.