XML file under the Project log Folder

[nisgupta]

What is the file which is of XML format Under the Project Log Folder ? What information it contain ?

Please update 

Thanks

Nishchal

[tristaanogre]

Which file do you mean?  If you mean the <project name>.mds.tcLogs file, that's the file that contains the links between the project MDS file and the logs for the individual executed test runs.  This is not a file that should be checked in and out of source nor is it necessarily recommended to manipulate it outside of regular functioning of TestComplete.  You CAN but, if done improperly, you could end up with lost data for test run logs.

[nisgupta]

Attached the screenshot .

[tristaanogre]

That's the log itself, all the record entries in the log in XML format.  Again, you can read it and do what you want... but it's not recommended to alter it. 

[nisgupta]

So it is the same log entries in XML format  that we see on TestComplete IDE under the Test Log? Attached the screenshot

[tristaanogre]

Yes.  There are other supporting files that go along with that XML to include files, screenshots, etc. 

[nisgupta]

Where we can see the information about this file in TestComplete documenation ?

Thanks

Nishchal

[tristaanogre]

There is no user documentation for those files because, as mentioned, they are not files that are typically used, utilized, altered, or read directly from any sort of script code or functionality.

Question:

What do you need to know about his file?  What are your intentions? What are you trying to do?

[nisgupta]

As I mention in other forum that we are interested in creating the issue in Jira if the log contain errors automatically. but TestComplete do not have this support to do automatically . We are looking for some kind of data to inject to Jira API to do this. That is why we wanted to know.

Thanks

Nishchal

[tristaanogre]

Rather than reading the file, what if you used the "OnLogError" event handler to call your API call to Jira to create the issue?  The "LogParams" that is generated in that event handler contain the contents of the error entry that is created.  Rather than parsing the file, you can intercept the error log entry itself and use that for pushing to the API.