vstest icon indicating copy to clipboard operation
vstest copied to clipboard

Deciding on behaviour of TPv2 for conflicting settings.

Open cltshivash opened this issue 6 years ago • 0 comments

  1. When there are conflicting settings, users communicating through TL should also get warning. Expected - Warning should reach the clients if there's a mismatch in the dlls configuration. Actual - Warnings don't go to the design mode client via the TL. Only Loggers will get the warnings.

  2. When 2 dlls passed like, first.dll with framework net46 and second.dll with framework net461 are passed. Expected - No warning should come, when compared to TPV1 Actual - Displays warning for first.dll with net46 framework, as framework net461 is used for run.

Sample O/P: Starting test execution, please wait... Test run will use DLL(s) built for framework .NETFramework,Version=v4.6.1 and platform X86. Following DLL(s) do not match framework/platform settings. UnitTestProjectNet46.dll is built for Framework 4.6 and Platform X86. Go to http://go.microsoft.com/fwlink/?LinkID=236877&clcid=0x409 for more details on managing these settings.

Passed TestMethod1 Passed TestMethod1

Total tests: 2. Passed: 2. Failed: 0. Skipped: 0. Test Run Successful. Test execution time: 1.0083 Seconds

  1. When 2 dlls psased like, first.dll with framework net46 and platform x86 and second.dll with framework net461 and platform x64. Expected: According to logic x86 will be the platform and net461 will be the highest framework version. And hence the dll ran will be first.dll. But that's not evident from the output. If you see the smaple o/p, user may not make out what dll ran. [usability]

Sample O/P.

Test run will use DLL(s) built for framework .NETFramework,Version=v4.6.1 and platform X86. Following DLL(s) do not match framework/platform settings. UnitTestProjectNet46.dll is built for Framework 4.6 and Platform X86. UnitTestProject3.dll is built for Framework 4.6.1 and Platform X64. Go to http://go.microsoft.com/fwlink/?LinkID=236877&clcid=0x409 for more details on managing these settings.

Passed TestMethod1

Total tests: 1. Passed: 1. Failed: 0. Skipped: 0. Test Run Successful. Test execution time: 0.7778 Seconds

cltshivash avatar Jan 01 '19 03:01 cltshivash