Forum Discussion
Right... so... what changed? We gave a recommendation of attaching the MHT file to the log which is then pulled back to the main TC machine used for execution. This would pull back MHT files from all CBT environments as they are executed. Is this not working?
Nothing changed.
we discussed about the Log.File statement to be put in Report script but again that script will be run as parallel with other script.
- tristaanogre5 years agoEsteemed Contributor
Unfortunately, that's not going to be possible due to how the test are run against the CBT environments. Think of each CBT environment run as being another machine running another copy of your project. So, you'll have 150 different MHT files that you will pull back and store.
- tristaanogre5 years agoEsteemed Contributor
Right. That's fine. I don't see any reason why that would be a problem. The log will pull back the files and such from the CBT environment per test run... that is, unless you're experiencing some other error that you haven't told us. But that is the recommendation... even if they are running in parallel, this should work because each log is kept separate per machine that it's run on.
- nisgupta5 years agoValued Contributor
Here is the error information that I have .
- tristaanogre5 years agoEsteemed Contributor
If you double click on the line that says "The parameter is incorrect", it will take you to the script/keyword test and specific line that generated that error. Also, check the "Additional Information" tab for that error entry as that will also give indication of further details. However, this doesn't appear to be a problem with the CBT execution (note that the MHT file IS actually attached to that log) but that there's something going on particularly in that machine at that point. More information is necessary
- nisgupta5 years agoValued Contributor
The error is at the line
Log.File("*\\CBT_WOAHOLD_Admin\\WOAHOLD Admin\\Log\\Results\\CBT WOAHOLD-001 Admin Page Holds Search and Edit.mht")
- tristaanogre5 years agoEsteemed Contributor
The asterisk makes it incorrect. The path name needs to be the fully qualified name for the file. What does the call for exporting the log use to indicate the target path? That's what you should use in Log.File....same pathing. You should be using something like "Project.Path" or something like that to indicate the root. It's not going to be able to log a file using the "asterisk" as the opening path.
- nisgupta5 years agoValued Contributor
Thanks for the Update
Here is another issue- Log.File create file1.mht as attached in the screenshot and it is located in the ....\Log\5_13_2019_2_53 PM_11_468\{ABA7496F-EFAF-4CEE-9732-23D562E3E296}\File1.mht
- tristaanogre5 years agoEsteemed Contributor
From the help for Log.File
Remarks
-
The method renames the file when copying it to the test results folder. The new name has the format
File<index>.originalExtension
. This approach helps TestComplete avoid naming conflicts when posting files. Below is a typical example of the code that might cause conflicts:Log.File("C:\MyFile.txt");
ChangeFileInSomeWay("C:\MyFile.txt");
Log.File("C:\MyFile.txt");If TestComplete does not rename the file when posting it to the log, the second call to the
Log.File
method would cause a naming conflict.
-
- nisgupta5 years agoValued Contributor
Thanks for the updates .
But here how it is working.
For e.g. Script 1 and Script 2 need to run on Window 10 and on Firefox 66 then Log.File will generate individual MHT report for Script 1 and Script 2.
Goal is to generate MHT report after Script 1 and Script 2 finished running. We have almost 150 CBT tests as the script are running on different OS/browsers .
We want to have Single MHT report after 150 CBT tests finished running.
Thanks
Nishchal
Related Content
Recent Discussions
- 2 days agoGane195