I'm trying to export my test cases from Microsoft Test Manager 2013 and i tried various tools but none is working.
I'm getting 2 different errors:
1) Must install microsoft.teamfoundation.build.client version 11.0.0.0 in the GAC
2) Object Reference not set to an instance of an object. Application has encountered Fatal Error. Please contact your System Administrator.
In case 2, i'm capable of connecting to the TFS. I get the error once i try to connect to the project.
Any ideas?
Related
I´m using Rational Rhapsody 8.3.1 and I tried to follow the ATG Tutorial, but when I press "Apply ATG" there's the following Error Message:
ERROR: ATG is not applicable on configuration TPkg_TheTestCalc::TPkg_TheTestCalc_Comp::DefaultConfig.
Please check Environment settings.
In the Environment Settings "MSVC" and "Debug" is selected (Code Generation with Visual Studio works). I tried it with different Versions of RR and different Versions of Visual Studio, but always the same issue.
Does anyone know this Problem or what to try next?
I create an SSIS package with VS 2013 SSDT-bi, I try to create a job in SQL Server 2012:
I add my package under Integration Services Catalogs, when I want to validate it says :
Package error : Pacakge migration from version 8 to version 6 failed with error 0xC001700A
The version number in the package is not valid. the version number cannot be greater than current version number
And when I try to create a new job it says :
The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.
I Googled and I found that VS 2013 SSDT-bi starts working with SQL Server 2014.
I want to know if there is a workaround for my issue or I have to download VS2012 and re-create my package ?
I did succeed in tricking it to work (changing the project/package XML). However, i would never recommend that, since it's gonna stop working at some point and give you further headaches.
Download VS 2012 SSDT (you'll probably need VS2012 shell as well), open packages there and redeploy.
EDIT: spelling :(
I'm getting the following error when trying to run a coded ui test from MTM:
Unit Test Adapter threw exception: Method not found: 'Void Microsoft.VisualStudio.TestTools.UITest.Extension.UITestUtilities.AddAssemblyResolveHandler()'..
All I'm looking for is a hint as to why this is happening, my project references look like this:
I'm using Visual Studio 2013 Update 4, The Test Controller and Agent too are 2013 Update 4.
I can queue a build, but when I try and run a test against the build using MTM, I get this error.
EDIT, Also using net 4.5.1.
EDIT 2: Everything runs locally in dev environment when tests are kicked off from Visual Studio. It's once I kick off the tests through MTM -> Controller -> Agent where the problem persists. The exact same message is thrown regardless of the test.
Check if the test run has all the necessary dlls in the test run directory, in the machine where test controller runs check the directory
"C:\Users\ username \appdata\Local\VSEQT\QTController\ testrunid \Deployment\"
I have found various iterations of this question across a number of websites, however so far I have not found anything that provides a full answer that worked.
I have just set up a number of Visual Studio Test Agents that all appear to be behaving and running most of the unit tests we are planning on initially running on them. However when I came to checking one of the unit tests it is failing on the line:
using (ShimsContext.Create()),
With the stack trace:
Result Message:
Microsoft.QualityTools.Testing.Fakes.UnitTestIsolation.UnitTestIsolationException: Failed to resolve profiler path from COR_PROFILER_PATH and COR_PROFILER environment variables.
Having read some other posts I installed Visual Studio 2013 on the test agent and confirmed it would run the test locally. I then set COR_PROFILER_PATH to the profiler that was being used on my machine which was installed at: “C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\IntelliTrace\12.0.0\Microsoft.IntelliTrace.Profiler.12.0.0.dll”.
It then failed in the same place with the trace:
Test method threw exception:
Microsoft.QualityTools.Testing.Fakes.UnitTestIsolation.UnitTestIsolationException: Failed to get profiler module handle 'C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\IntelliTrace\12.0.0\Microsoft.IntelliTrace.Profiler.12.0.0.dll'. The specified module could not be found ---> System.ComponentModel.Win32Exception: The specified module could not be found
The suggestion is the profiler has been loaded under a separate process and can't be used. Has anyone had any success with this or similar set ups? At a fundamental level can Visual Studio Test Agents run tests with Fakes?
Thanks
I know this is a bit old, so the OP probably got his answer, but for anyone else, I opened a ticket with Microsoft on this issue, and the answer we came to after an hour and a half of looking at my setup for this problem:
Microsoft.QualityTools.Testing.Fakes.UnitTestIsolation.UnitTestIsolationException: Failed to resolve profiler path from COR_PROFILER_PATH and COR_PROFILER environment variables.
, was that I was using mstest.exe and I should have been using vstest.console.exe. In my case it was because I have Fakes test in my code now.
I'm using Visual Studio 2013 update 4.
I was having the same issue with a project I was working on. I found this issue noted:
https://connect.microsoft.com/VisualStudio/feedback/details/832744/unable-to-debug-shims-based-tests-unittestisolation-exception
There was an attached project, so I downloaded the project and ran the only unit test. Same error - the unit test was not successful. However, I right-clicked on System under the References, and clicked Add Fakes Assembly. Once it had generated the fakes for System and mscorlib, voila! The test turned green.
I was able to reproduce the issue in my project - I did not have fakes being generated for System. Once I generated them for System, my tests went from red to green!
Side note -- If you don't want to generate ALL of the fakes for System and mscorlib, you can modify the .fakes files like so.
mscorlib.fakes:
<Fakes xmlns="http://schemas.microsoft.com/fakes/2011/">
<Assembly Name="mscorlib" Version="4.0.0.0"/>
<StubGeneration Disable="true" />
<ShimGeneration Disable="true" />
</Fakes>
System.fakes:
<Fakes xmlns="http://schemas.microsoft.com/fakes/2011/">
<Assembly Name="System" Version="4.0.0.0"/>
<StubGeneration Disable="true" />
</Fakes>
I could not disable ShimGeneration for System.fakes - the test would fail.
I hope this fixes the problem for someone else - the error is extremely vague!
(I'm assuming your Test Agent is also a Build Agent.)
Is the build service version synced with the Visual Studio version which is installed?
I had the same issue in the following environment:
TFS 2013
Build Server w/ TFS 2013
Visual Studio 2015.3 installed in the build server
When I updated the TFS version on the build server to 2015.3, the issue stopped happening.
I know it may not make sense, but solved the problem as the TFS 2015 XAML Build is compatible with TFS 2013.4 app tier.
I am attempting to install Visual Studio 2010 Agents for Test Controller / Test Agents so I can create Load Tests on my local machine. When attempting to install the Test Controller I recieve the following message in the configuration summarry
From the installation log I found the following error messages:
The existing connection string for controller MyComputerName:6901 is {this is blank}
System.MissingMethodException: Method not found: 'Boolean
Microsoft.VisualStudio.TestTools.WebStress.LoadTestDatabaseCounterWriter.IsDatabaseUpgradeFromRTMNeeded(System.Data.SqlClient.SqlConnection)'.
at
Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateAndUpgradeLoadTestSchemaIfRequired(String
loadTestConnectionString, String directoryContainingSchemaFile) at
Microsoft.VisualStudio.TestTools.ConfigCore.ControllerConfiguration.UpdateLoadTestDatabase(ControllerConfigurationUpdatePack
updatePack, DelegateStatusUpdate statusListener)
Failed to configure load test database.
Problem solved!
Briefly, only Visual Studio 2010 Service Pack 1 is missing, and a DLL doesn't contain a method that is invoked by the Test Controller Configuration Tool.
Solution: install VS 2010 Service Pack 1.
Reason: Microsoft.VisualStudio.QualityTools.LoadTest.DLL does not contain a Database checker method that is invoked by the configuration tool, so an exception is thrown, and the configuration is failing. After upgrading to SP1, the DLL updates successfully and the missing method can be found there.