visual-studio-2013,coded-ui-tests,vstest
After much investigation and NextInLine's help, we found that the issue was with how our test was accessing and using the msxml6.dll. We reapired the installation of this dll and others, and resolved the issue.
visual-studio,azure,windows-runtime,windows-8.1,vstest
That was quite a funny. Error message Error: Unit tests for Windows Store apps cannot be run from BUILTIN\administrato r or TR\xakpc user accounts. Please run tests using a user account fro m which process with medium and low privileges can be launched. means that i need simple local user...
unit-testing,visual-studio-2013,mstest,vstest
Following a reboot - problem resolved!
visual-studio-2012,mstest,unit-testing,vstest
I needed to surround my test dll path with quotes: var testProcess = new Process { StartInfo = new ProcessStartInfo { FileName = @"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe", Arguments = _testDllPath.Replace(_testDllPath, '"' + _testDllPath + '"'), UseShellExecute = false, RedirectStandardOutput = true, CreateNoWindow = true } }; ...
msbuild,mstest,xunit,vstest,visual-studio-test-runner
After some research found that I will need to pass the test adapter for visual studio, which makes the tests discover-able. /TestAdapterPath:"packages\xunit.runner.visualstudio.0.99.2 Here's the complete command, c:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe" /TestAdapterPath:"packages\xunit.runner.visualstudio.0.99.2" "C:\UnitTest\MyTests.dll" /settings:"C:\UnitTest\output.runsettings" /UseVsixExtensions:"true" /InIsolation /Logger:"trx" There is a nuget packahe...