Forum Discussion

wmtan01's avatar
wmtan01
Contributor
5 years ago

Exporting Logs in a single file thats not MHT

Hi,   We've been exporting our logs into MHT using TestExecute's Command Line Interface /ExportLog because of it being a single file and easy to open up and just read. So far we're only able to ope...
  • hkim5's avatar
    hkim5
    5 years ago

    thats a valid concern you bring up about IE being deprecated. Perhaps you could save the logs in html format  (using /ExportSummary) instead, which can be opened by any other modern browser

    there is also a zip-ping object in testcomplete called the slpacker. this is a built in object that you can use to zip up whatever files you need : https://support.smartbear.com/testcomplete/docs/reference/program-objects/slpacker/index.html (this would have to be done inside your test scripts, as opposed to the CLI)

    typically in a CI environment, there may be a max # of logs kept, in which case TestComplete will generate and store the relevant test logs per build (for jenkins, azure dev ops, etc.) within the temp dir, or within the workspace of the build itself.

    if we are trying to keep old test artifacts, then i think you have the right idea about using the CLI arguments of exportlog or exportsummary. 

     

hkim5's avatar
hkim5
Staff

thats a valid concern you bring up about IE being deprecated. Perhaps you could save the logs in html format  (using /ExportSummary) instead, which can be opened by any other modern browser

there is also a zip-ping object in testcomplete called the slpacker. this is a built in object that you can use to zip up whatever files you need : https://support.smartbear.com/testcomplete/docs/reference/program-objects/slpacker/index.html (this would have to be done inside your test scripts, as opposed to the CLI)

typically in a CI environment, there may be a max # of logs kept, in which case TestComplete will generate and store the relevant test logs per build (for jenkins, azure dev ops, etc.) within the temp dir, or within the workspace of the build itself.

if we are trying to keep old test artifacts, then i think you have the right idea about using the CLI arguments of exportlog or exportsummary. 

 

wmtan01's avatar
wmtan01
Contributor
5 years ago

I tried the html file for the TestExecute CLI (I think its still with the /ExportLog not /ExportSummary parameter) and it resulted to a collection of files, not a single file which is my concern.

 

I have not used slPacker yet but I've been using Log.SaveResultsAs (https://support.smartbear.com/testcomplete/docs/testing-with/log/working-with/exporting/index.html) for our non CI execution, this results to a zip file. if push comes to shove, we'll have to switch to zips instead of mhts, though that adds a step to our QAs who check the results to unzip the files and know which one to open.

  • sonya_m's avatar
    sonya_m
    SmartBear Alumni (Retired)
    5 years ago

    Hi wmtan01 , did you give the slPacker Object a try? Was it a success?

    • wmtan01's avatar
      wmtan01
      Contributor
      5 years ago

      Hi,

       

      I did not yet have a change to use it but reading from the documentation, I believe it will do similar things to Log.SaveResultsAs with the way I plan to use it. I don't think other than MHT or Zip there is another way for us to export logs from TestComplete/TestExecute

       

      With that being said, I think I'll close this thread accepting the slPacker solution which generates ZIP files