cancel
Showing results for 
Search instead for 
Did you mean: 

TestComplete and vsTest in DevOps, Test Agent throwing exceptions when project is integrated w/TFVC

SOLVED
Highlighted
New Contributor

TestComplete and vsTest in DevOps, Test Agent throwing exceptions when project is integrated w/TFVC

Similar to https://community.smartbear.com/t5/TestComplete-General-Discussions/Failed-to-initialize-the-tfs-api..., the solution for whom is insufficient.

 

I've recently started trying to implement TestComplete tests as part of our DevOps Testing release pipeline.  I've currently got what is effectively a proof of concept test project in place; it doesn't do anying complex, just pushes some buttons and completes.  Everything operates as expected, except each time the release pipeline runs per agent I get a pop-up to the effect that the Microsoft.TeamFoundation.Client assembly cannot be loaded.  The entire process halts until this (And sometimes other, effecitvely identical) popup(s) are manually cleared. 

 

I understand from the previously linked post that this is due to my utilizing the in-client TFS Source Control integration, but that leaves me at an impasse.  If I remove that integration then the errors will disappear, but I'll have to find another, more error prone method of source control for this and future projects.  If I leave the integration in, my Automated testing suites will require manual intervention each time which is cumbersome and not scalable.

 

Is there any way to disable Source Control connection on startup, since there really is no need for it to connect just to run some tests?  Is there a separate process I could use to run these tests that wouldn't invoke the TestComplete client?

Capture.PNG

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Community Hero

Re: TestComplete and vsTest in DevOps, Test Agent throwing exceptions when project is integrated w/T

1) I daresay most of us work in a professional environment.  There are still many source control tools available.  If you are not able to choose your own, then that's another story.  Perhaps you can make a case for changing to a better one.

 

2) Here's where you can read about TestExecute.  It is licensed separately.

https://support.smartbear.com/testexecute/docs/index.html

View solution in original post

5 REPLIES 5
Highlighted
Community Hero

Re: TestComplete and vsTest in DevOps, Test Agent throwing exceptions when project is integrated w/T

1) How are other source control more error prone?  What have you tried and what happened?

2) Have you tried the run using TestExecute instead of TestComplete?  If so, what happened when you tried?

Highlighted
New Contributor

Re: TestComplete and vsTest in DevOps, Test Agent throwing exceptions when project is integrated w/T

1) I didn't mean that other source control systems are more error prone, I meant that I would need to use a different process to include this project in source control; likely adding the project to an existant Visual Studio project and managing it through there, which has a number of problems.  This is in a professional environment, I don't have the luxury of using other source control systems.

 

2) I haven't tried that, as I'm not familiar with that product.  Is it included under a TestComplete floating license, or would that need to be licensed separately?

Highlighted
Community Hero

Re: TestComplete and vsTest in DevOps, Test Agent throwing exceptions when project is integrated w/T

1) I daresay most of us work in a professional environment.  There are still many source control tools available.  If you are not able to choose your own, then that's another story.  Perhaps you can make a case for changing to a better one.

 

2) Here's where you can read about TestExecute.  It is licensed separately.

https://support.smartbear.com/testexecute/docs/index.html

View solution in original post

Highlighted
New Contributor

Re: TestComplete and vsTest in DevOps, Test Agent throwing exceptions when project is integrated w/T

1) I apologize if I offended, I didn't mean to imply any relative level of professionalism, I just meant changing source control systems wouldn't be a simple process, and regardless the issue isn't with TFSSC as a system but with how TestComplete handles projects loaded with the limited purpose of executing tests as part of an automated pipeline vs. projects loaded for a more generalized test development process.

 

2) From what I see, TextExecute should resolve my issue handily.  it might be a bit premature, but considering the timeline on which I can vet it fully is unclear I'm going to go ahead and call this one resolved.

Highlighted
Community Hero

Re: TestComplete and vsTest in DevOps, Test Agent throwing exceptions when project is integrated w/T

TestExecute is the same "engine" as TestComplete, only without the debugging and development environment.  Anything you write and run in TestComplete can be run in TestExecute as a command line.  So, I don't foresee any problem with you vetting it on a functionality level... it would simply be on how you would implement it in your environment.


Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff
----

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
New Here?
Join us and watch the welcome video:
Top Kudoed Authors