fake-xrm-easy
fake-xrm-easy copied to clipboard
I cannot run my FakeXrmEasy Unit test on visual studio 2019 community Edition
Hello everybody,
I develop a CWA with VS2019 latest update then I create the Unit Test following the FakeCrmEasy
the Unit Test Start but then it stops(no results displayed); I experienced the Unit test issue with VS2017Community edition that then I fixed but with VS2019Community I am not able to solve it
please help me
'testhost.exe' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'testhost.exe' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\Extensions\TestPlatform\testhost.exe'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled. 'testhost.exe' (CLR v4.0.30319: testhost.exe): Loaded 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\Extensions\TestPlatform\Microsoft.TestPlatform.CoreUtilities.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
.............................
'testhost.exe' (CLR v4.0.30319: Dependency finder domain): Unloaded 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\Extensions\TestPlatform\Microsoft.VisualStudio.TestPlatform.ObjectModel.dll' The thread 0x3f3c has exited with code 0 (0x0). The thread 0x4114 has exited with code 0 (0x0). The program '[8872] testhost.exe' has exited with code 0 (0x0).
Hello everybody,
I tried to debug the fake XRM unit test also in VS 2017 community edition but the test doesn't start !!
please help me.
'testhost.exe' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled
.........
The thread 0x5060 has exited with code 0 (0x0). The thread 0x4ee4 has exited with code 0 (0x0). The program '[22264] testhost.exe' has exited with code 0 (0x0).
@Gmanunta, code 0 mean you don't have errors, so please stop posting million lines of logs :) To be serious, I have problems with tests too. Usually it helps to update xunit NuGets to last version and then revert repo to original state. That's why I prefer MSTest2, but I don't establish rules here :)
Hello @FixRM, thank you for your help and I apologize for getting back to you late; You are right, a lot of logs lines but without sense at the end( so I will edit and I will keep this conversation shorter!! :D). I tried to upgrade/revert Xunit via NuGet but the unit test doesn't work!
thanks a lot !!
Some common (if not most) issues are due to having 2 different test adapters / test frameworks. If you use Xunit, please uninstall any MS test adapters (like MSTest). Usually that's the very first thing I do immediately after creating a unit test project.
Also make sure you have xunit.runner.visualstudio installed, and that you have cleared the TestExplorerCache as explained in the README at the bottom of this repo.