Attaching zip file to log. Opening zip in mht

[jhgreen]

Currently I am attaching a zip file to our logs if we encounter an error.

When I export the log file to an mht and launch mht in Internet explorer.

I am unable to open up the zip file.

I imagine this is an issue with Internet Explorer, has anyone encountered this issue and any workarounds to suggest.

[Marsha_R]

What's the zip file for?

[jhgreen]

Basically the zip file is for the developer logs. Usually when we get a test failure that the developer needs

to investigate we send them the mht file but sometimes they also request these developer logs to help them debug the issue.

[Marsha_R]

I wouldn't have expected IE to open a zip file, but maybe just because I haven't tried.  Can you open the zip file by just clicking on it?

[jhgreen]

It works when I click on the file link from TestComplete but when I click on the link in the mht file in internet explorer

it opens in another tab and immediately closes the tab. So, I imagine something went wrong.

[Marsha_R]

Try one of the other options like .pdf and see if that works out for you.  We always had trouble with mht.

[jhgreen · Accepted solution]

I tried pdf and that did not seem to work for me. We will just with downloading it from TestComplete and send it along

with the mht file. Thanks for your responses.

[AlexKaras]

Hi,

> It works when I click on the file link from TestComplete

Considering the above I am assuming that you are talking about the link to the file referenced in the log using Log.File() method.

If my guess is wrong, then you may consider Log.File() method.

In any case, check if the link to the file references local disk (e.g. C:\Project\...) or the network/UNC path (e.g. \\my_pc\Projects\...). In the former case it is expected that the file will not be opened as is will be absent on the given local developer's box.

If you cannot reference the file for Log.File() using UNC notation, you may try to craft UNC path in code and put it into the log as an Additional Information for the same Log.File() method. In this case developers will be able to copy the UNC path from the Additional Info log tab and navigate to the file.