Testcentric GUI gets stuck thinking a test is running even across reboot

[symbolgimmicks]

Describe the bug
It's possible to get the testcentric gui in to a state where you can never run tests again.

It enters a state where, whenever you attempt to execute a test, you receive pop up. The pop up tells you there is already a test running. You are given a Yes/No option as to whether or not you want to stop that test in order to (presumably) start the one you desired.

However, either answer results in testcentric waiting a few moments and then closing. Every attempt to run any test, from any dll, from that point on, will repeat that pattern. Rebooting the system does not change the behavior, either. Choco uninstall/install also does not remove the issue.

If you do not make a selection in time, test centric will just close on its own.

Reimaging the system is the only way I've found to alleviate the defect.

To Reproduce

This defect is incredibly sporadic. It may have something to do with force quitting testcentric, but in my test experience it has been incredibly unstable (can't run more than 1 test at a time, can swap dlls after running single test in one) and just spins until it throws an exception while closing after running any test.

Can't rule out that the inability to close could be related to what I do or how I make my tests but I can't disclose that information.

Expected behavior
Rebooting the system should cause test centric to forget any tests were ever running, no matter what. The Yes/No buttons on the pop up should have an effect corresponding to the popup's text.

Screenshots

Environment (please complete the following information):

• TestCentric Version 1.6.3
• OS: Windows 10

[CharliePoole]

Please try this on TestCentric 1.6.4 and 2.0.0-beta5 if you are able.

[CharliePoole]

@symbolgimmicks Have you been able to repro this on either of the later versions I mentioned?

[symbolgimmicks]

I have someone on my team who is interested in trying it now as they just experienced the same issue on a separate system using an older build. I am instructing them to try the version you have recommended, now.

[symbolgimmicks]

1.6.4 was tried and did not remediate the issue. 2.0.0-beta5 has not been attempted. No ETA on when that will be tried.