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

[nisgupta]

yes we will use OnLogError Event but how TestCOmplete can access our Jira System ? With TestComplete script we can only access BugZilla and visual studio team system

Thanks

Nishchal

[tristaanogre]

API calls can be made in code using https://support.smartbear.com/testcomplete/docs/reference/program-objects/aqhttprequest/index.html. So, while there is not an object SPECIFICALLY for Jira, you can write code to make the calls.

[nisgupta]

@tristaanogre 

I have tried the code as mentioned in the above link and it ges the status 200. I have never used this utility before . 

Can we use the REST API code for Jira here ?

Thanks

Nishchal

[tristaanogre]

You should be able to.  That's my point... that you can call whatever API requests you want to within the OnLogError event handler.  I'm leaving it up to you to write the code.  But yes, you shoiuld be able to write the API code here...  Different objects, possibly, but the code should be able to be used.

[nisgupta]

@tristaanogre 

Ok,

Here is another thing

Our TestComplete script fails for many reasons for e.g.

Object properties change due to the change in application 

application is down

Script itself has some errors 

Is there a way we can identify the type of errors automatically so that we can assign to developers or QA person ?

Let me know if you need more details 

Thanks

Nishchal

[tristaanogre]

LogParams object in the OnLogError event handler contains the message text for the error being logged.  You can parse out the text to look for certain patterns, keywords, etc.  

[SeumasMack]

@tristaanogreIt appears you are answering a question I've been trying to get SmartBear support to respond to.  As my team keeps having merge conflicts with the ".mds.tcLogs" file, I wrote to SmartBear support and asked them if it would be okay for me to include that file in our ".gitignore" file in Bitbucket.  Before doing so, however, I wanted them to confirm for me that I wouldn't be wrecking anything or causing others problems when trying to run tests at a later date/time.  Just to confirm here, mate, you are saying it's okay to ignore the .mds.tcLogs file, correct?

[tristaanogre]

---

@SeumasMack wrote:

@tristaanogreIt appears you are answering a question I've been trying to get SmartBear support to respond to.  As my team keeps having merge conflicts with the ".mds.tcLogs" file, I wrote to SmartBear support and asked them if it would be okay for me to include that file in our ".gitignore" file in Bitbucket.  Before doing so, however, I wanted them to confirm for me that I wouldn't be wrecking anything or causing others problems when trying to run tests at a later date/time.  Just to confirm here, mate, you are saying it's okay to ignore the .mds.tcLogs file, correct?

---

Yes. 

From the help, indicating files that TestComplete, when integrated with source control, are not included and the reasons why.

Note, that the following files are not added to the source code control:

• .tcCFGExtender - This file holds tester-specific settings for the project suite (such as the workspace layout).

• .tcLS - This file contains tester-specific settings for the project suite or project (such as local paths to tested applications, local values of project and project suite variables).

• .bak - Backup copies of script units.

• .tlb - This is a type library that contains declarations of events used in the project.

• .tcLogs - This file contains information on the project suite or project logs.

• Log files.

• Project item files that are physically located outside of the project suite folder.

To add detail to the .tcLogs files, these actually are a "linking" file for the project indicating which log entries are associated with the MDS file and where to find them.  Everytime a new log entry is created, that file is updated.  Because you don't need to version control/source control log files (they aren't source, they are output), you can safeily ignore them... and any other files in the list I just provided.

[tristaanogre]

In fact... as a quick edit to my post... everything that I listed SHOULD be ignored in your .gitignore file.  There is no need for any of them to be version controled and you may even cause problems if you do so.

[SeumasMack]

Thanks, mate.  My team and I are brand new to TestComplete and it has given all of us so many headaches.  Two of my Test Automation Engineers have moved back over to the Manual Test Team because they refuse to work with TestComplete. 

In any event, I appreciate you taking the time to respond to my inquiry.  I'm going to update our .gitignore file and include all of the items you presented.

Cheers,

Seumas