chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
Welcome to Typemock Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.
0 votes
Hi

Testing out 6.0.1.0 and getting "The connection to the controller was lost." as the last entry in the run log (Test Run Rrrors and Warnings section) on some, but not all of the test runs. All the tests are green, but the test run is classified by VS as failed.

Any ideas?
asked by (2k points)

6 Answers

0 votes
Hi,

This seems like a bug we encountered and already have an internal fix for. I'm emailing you a link to the patched installer - can you let me know if it indeed resolves the same issue?

Thanks,
Doron
Typemock Support
answered by (16.5k points)
0 votes
Hi,

Ive actually encountered this a few days ago.

After some research we concluded that the message is reported when the mstest runner does not ends properly.

In our case it was caused by the application code, and we manage to fix that with no relation to Isolator.

I'm guessing that if this just started to happen after the upgrade to 6.0.1, you should wait for the mentioned patch.

:| just thought to add some additional info
answered by (6.6k points)
0 votes
I also started seeing this issue after installing 6.0.1.0.

Has the patched version been successful in fixing the issue? I could also try the patched version to see if it resolves my issue.
answered by (140 points)
0 votes
Hi

From the responses we got from our users it seems that the patch fixed the issue.
I'm sending you a link to download the patch, please try it and let me know the results.
answered by (35.5k points)
0 votes
Hi Doron,

I have the same problem. My tests are canceld with the error "The connection to the controller was lost." We use version 5.3.4.0 of TypeMock.

What is the solution for this issue?

Thanks for your help.
Regards,
Thomas
answered by (140 points)
0 votes
Thomas,

Can you upgrade to the latest version? A bug causing this behavior has been resolved in version 6.0.1.

Doron
Typemock Support
answered by (16.5k points)
...