Ask a Question

SessionCreator / ExportLog

SOLVED
SK2020
Occasional Contributor

SessionCreator / ExportLog

Hi, 

 

I'm using TeamCity for CI and after the execution, I'm getting log files to see the results. I'm using SessionCreator.exe commands from this documentation https://support.smartbear.com/testcomplete/docs/working-with/automating/session-creator/index.html

 

I have several question about /ExportLog:file_name (or /el:file_name) command.

 

1.   Log file name convention – can we use a cmd line (DOS) parameter to insert current date/time in the output file names as part of the cmd line execution?

2.   Do we create a new log every time (overwriting the previous one) or at least make a backup of the last one before creating a new one?

3.  Do we clean up other items in the folder (e.g. report files, etc.) or keep creating new ones in the same folder for a certain duration before we manually(?) clean them up? 

 

Thank you for your answers.

1 ACCEPTED SOLUTION

Accepted Solutions
hkim5
Staff

Re: SessionCreator / ExportLog

1. /ExportLog argument should be able to take in cmd line variables (idk exactly what DOS stands for, but I've used env. variables from diff. agents and thats worked i.e things like {WORKSPACE} or etc. when using some sort of an agent based capability from other CI tools)

2. if you are time stamping your logs, this would be irrelevant. as a matter of fact, if there is a preexisting file with the same name- your command will error out (kind of a quirk of the session creator utility)

3. per the second comment of (2), I would suggest including a first set of commands to clean up the designated report folder using something like 

CD "your_report_dir"
DEL /F/Q/S *

such that you dont get the exportlog error of preexisting report file 

Best,
Justin Kim

View solution in original post

2 REPLIES 2
Marsha_R
Community Hero

Re: SessionCreator / ExportLog

Did you try any of the things you asked about?  What happened when you did?


Marsha_R
[Community Hero]
____
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame
hkim5
Staff

Re: SessionCreator / ExportLog

1. /ExportLog argument should be able to take in cmd line variables (idk exactly what DOS stands for, but I've used env. variables from diff. agents and thats worked i.e things like {WORKSPACE} or etc. when using some sort of an agent based capability from other CI tools)

2. if you are time stamping your logs, this would be irrelevant. as a matter of fact, if there is a preexisting file with the same name- your command will error out (kind of a quirk of the session creator utility)

3. per the second comment of (2), I would suggest including a first set of commands to clean up the designated report folder using something like 

CD "your_report_dir"
DEL /F/Q/S *

such that you dont get the exportlog error of preexisting report file 

Best,
Justin Kim

View solution in original post

cancel
Showing results for 
Search instead for 
Did you mean: