Are you running the TestExecute tests on the same machine you developed the project on or is it a different machine?
If it's a different machine, it is possible that, on that machine, the test items that are not running have become de-selected if someone was doing some sort of debugging on that machine. I believe this is something that is typically stored in the tcLS file for the project. I think that file can be safely deleted on the machine in question and it will be recreated with the defaults when the project is re-opened. Try that and see if this corrects your problem.
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.
