Forum Discussion
Hi,
yesterday me and a coworker where able to see this in Testcomplete:
We have an Onstop Event which is just the logoff from our application. The Test ran and we could see the click on the logoff button. Our application went into “no response”. This is where the test are for. Our DEV people are searching for an error in our application. Anyway after several minutes our application window disappears but we could still see the Testexecute widget for about 5 minutes. When the Testexecute widget disappears too as well as Testcomplete. We restarted Testcomplete and where was no log of the Test. Where even were no Windows logs of the crash of our application or Testcomplete/Testexecute. So Testcomplete/Testexecute could as well have crashed first and took our application with it.
Additionally I’ve found false positive tests in QAComplete. The result is shown as passed but if we look into the results, the log stops in the middle of the test and the other test steps are just missing without any error.
So I think Testexecute crashes and QAC don’t get it.
Did you open a support Ticket? It might help Smartbear.
Regards
Tom
Howdy Tom, thanks for the reply and sharing your info as well... in my case I don't "think" its the same situation as per an experiment I tried:
so, I began to wonder if it was QAComplete... or TestComplete... etc...
I created a collection of the exact same tests... in the exact same order.... and ran using ONLY TestComplete this time and NOT QAComplete.... the entire suite/collection, ran, in approx 3.5 hours!!!! Perfect!!!!
Not one test did NOT run, and not one test took anything near over 10-15 minutes... so, they ran as they should.
So, what I know so far, when running using QAComplete... I have issues and that same suite of tests will take easily over 12 to 14 hours (!!!) ... whan running only using TestComplete, as ran as it should.
I will run that same suite again, this evening, using only TestComplete again and see if it still runs as expected... under 4 hours, no tests missing.
So, so far, "seems" Might be an Issue with QAComplete and my tests...
Have not logged a bug yet... wanted to see if I could gather more info....
Related Content
Recent Discussions
- 3 months agopratikshap