TestExecute crashes with no log produced
Again, I have submitted a ticket on this but hope somebody else may have encountered this issue or have some advice and suggestions . The problem is that TestExecute starts running my script and t...
Forum Discussion
I saw this again yesterday on my shiny new physical box with everything (memory, processor, etc.) maxed out.
Within a period of an hour "all" scripts started failing, with the same error a test complete log was not being produced.
ERROR: 'TestCompleteLogs\index.htm' doesn't match anything: 'TestCompleteLogs' exists but not 'TestCompleteLogs\index.htm'
. I investigated and determined that not all scripts were failing, but just the scripts attempting to access the QA.xlsx file.
However, at the same time these scripts were failing on one box, they were working on another box. (using subversion to update the xlsx file before running the test) with the same QA.xlsx file
After some tinkering with the excel file, the scripts magically started working when run against the QA.xlsx excel sheet.
My theory at this point is that due to some combination of the box environment and the excel spread sheet the DDT Ace driver is hitting some kind of error which Test Execute does not handle properly (e.g. catching exception or whatever). At that point, TestExecute just gracelessly crashes.
Hi Curt,
Have you reported this to Support (https://support.smartbear.com/message/?prod=TestComplete) referencing this thread?
There is a chance that they will provide you with some internal build of TestExecute with additional debug logging enabled or something like this that will make it possible for you to provide them with crush dump\log for further investigation...
Thanks Alex. I have been working on this with smartbear support for several months and we have not determined any helpful information. However, I will add this latest information and your suggestion and see whether they have anything.
Regards, Curt
