I deleted both the .tcls and tcls extender and did not see any difference.
It is believed that this is related to the other issue (Test Complete crashes with no log produced).
Hrm... that is strange. It sounds like you're executing, somewhere, some sort of illegal code that is blowing stuff up, like in an event handler or something.
Is it possible to zip up your project and send it over to me? I wouldn't mind taking a look. You can send it via private message here if you want and I can see if I can find something going on. In the meantime, take a look at your "OnStopTest" event handler (if you have one) and see if there's anything odd going on in there.
Thanks Robert. I am not sure whether this is related to the other issue (TestExecute crashing with no log) or not.
Here's my stop script.
function GeneralEvents_OnStopTest(Sender)
{
// putFirstLine("C:/TestData/howFar.txt", " 5/14 general events on stop test reached")
// Log.Message("5/14 - about to save results on stop test event");
Log.Message("GeneralEvents_OnStopTest event handler");
var temp = Log.SaveResultsAs("C:\\TestCompleteLogs\\", 1, true);
// Log.Message("done saving results");
}
When this occurs I do not see any difference between a complete test execution and a partial execution in the logs. My zipped script is about 439 meg so a) I don't think it can be easily mailed and b) there may be some IP issues with sending it out. Though I do appreciate the offer very much.
Regards.
Have you tried commenting out the code for that event handler and see what happens? I mean, it looks pretty innocuous, but iif you just turned it into an empty "do nothing" function, perhaps with nothing else in there but the Log.Message() call, and see if the same issue occurs. It could be that the Log.SaveResultsAs may be the issue itself if, for some reason, it's not liking doing the Log save in the midst of an event handler.
Worth a shot at least. I'm still pondering the possibility of the DDT.CloseDriver being an issue... but, who knows, could be two unrelated problemts.
