Thanks for the updates .
We have one more challenging issues. How can I run this script ? I have attached the CBT workspace screenshot showing that if the script is put in the CBT workspace then it will fail.
Well, first of all, if this is a different problem than the OP... would be better if it was it's own thread.
Second of all... I'm not entirely sure what you're asking. If a script is added to a workspace, it will attempt to run. If it fails, what are the errors? What messages? HOW exactly does it fail? Just saying "If I put it here, it fails" doesn't tell me much of anything.
We want to export the MHT report after running the CBT tests.
our CBT tests are running against different OS and Browsers
Once the CBT tests finished running then we want to export the MHT report.
We do have MHT report script which we want to run all the tests finished.
Now if we add the script the CBT test workspace then in CBT all the test script run in parallel and so the report script will run in parallel too.
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?
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.
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.
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