Forum Discussion

chicks's avatar
chicks
Regular Contributor
10 years ago

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...
tristaanogre's avatar
tristaanogre
Esteemed Contributor
9 years ago

Question: Are you making sure that you call DDT.CloseDriver on your Excel driver before you create another instance? I know for CSV files there's a maximum number of connections that you can have open before DDT.CSVDriver starts returning errors about being unable to open another connection.

 

If you're consistently having problems with opening a LOT of Excel connections, that would be where I'd start checking... basically, a rule of thumb is that, for every DDT.ExcelDriver call, you should have a corresponding DDT.CloseDriver call to close the Driver object when you're done using it.  Something like:

function MyTestCase() {
    var xcelDriver;
    xcelDriver = DDT.ExcelDriver('C:\\MyDocs\\MyXcel.xlsx', 'TestSheet', true);
    
    //do some stuff

    DDT.CloseDriver(xcelDriver.Name);
}
chicks's avatar
chicks
Regular Contributor
9 years ago

Hey Robert,

 

I noticed with the latest set of crashes that it was  failing instantly.  The first thing my scripts do is use the DDT driver to fetch some global information.  Prior to that TestExecute would crash after proceeding to the actual separate tests.  I conclude from that that the DDT (ACE) driver did not like the combination of spreadsheet / environment.  

 

Short Version:  It looks like it crashed on the initial opening of the ddt.exceldriver before I had any chances to close it or open more drivers....

 

Regards, , Curt