cancel
Showing results for 
Search instead for 
Did you mean: 

Is there a way to report the bug to JIRA on test failure through framework code. ??

SOLVED
Highlighted
Occasional Contributor

Is there a way to report the bug to JIRA on test failure through framework code. ??

Ex : 

Set LastResult = IntegrationObject.GetLastResultDescription Select Case LastResult.Status Case 0: MsgBox "The project run has finished successfully." Case 1: MsgBox "Warning messages were posted to the test log." Case 2: MsgBox "Error messages were posted to the test log." // ******************* code to log the defect to JIRA ???? ******************* End Select
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Community Hero

Re: Is there a way to report the bug to JIRA on test failure through framework code. ??

Here's the top level help topic on integrating with issue tracking systems.  Walk through this for getting the information you need.

https://support.smartbear.com/testcomplete/docs/working-with/integration/issue-tracking/index.html

 

Note that the JIRA interface is a Script Extension and, as far as I can tell in reading, it's not something that can be done via script code to report a bug.

Just as a side note:

I don't personally like the idea of having automated tests send the bugs to the bug tracking system.  Case in point, my current project.  I recently ran into a situation where a test case was failing.  Nothing was working properly at all and it initially presented as a bug.  Running as test automation, each time I run the test, the same error is generated.  If I had test automation set up to send the error as a bug, each test run it would create a new bug.  A lot of code and such would need to be written to check to see if the bug had already been reported and, if so, to skip reporting.  Turns out, it was not a bug but an undocumented configuration requirement.  If TestComplete had reported it as a bug, we'd have all these useless bug reports in our tracking system.

 

Notifying of errors via e-mail or other messaging is one thing.  This prompts the automation team to investigate and triage the situation to determine if it's really a bug.  But automatically generating bug reports seems like a bad path.


Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff
----

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available

View solution in original post

3 REPLIES 3
Highlighted
Community Hero

Re: Is there a way to report the bug to JIRA on test failure through framework code. ??

Here's the top level help topic on integrating with issue tracking systems.  Walk through this for getting the information you need.

https://support.smartbear.com/testcomplete/docs/working-with/integration/issue-tracking/index.html

 

Note that the JIRA interface is a Script Extension and, as far as I can tell in reading, it's not something that can be done via script code to report a bug.

Just as a side note:

I don't personally like the idea of having automated tests send the bugs to the bug tracking system.  Case in point, my current project.  I recently ran into a situation where a test case was failing.  Nothing was working properly at all and it initially presented as a bug.  Running as test automation, each time I run the test, the same error is generated.  If I had test automation set up to send the error as a bug, each test run it would create a new bug.  A lot of code and such would need to be written to check to see if the bug had already been reported and, if so, to skip reporting.  Turns out, it was not a bug but an undocumented configuration requirement.  If TestComplete had reported it as a bug, we'd have all these useless bug reports in our tracking system.

 

Notifying of errors via e-mail or other messaging is one thing.  This prompts the automation team to investigate and triage the situation to determine if it's really a bug.  But automatically generating bug reports seems like a bad path.


Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff
----

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available

View solution in original post

Highlighted
Community Hero

Re: Is there a way to report the bug to JIRA on test failure through framework code. ??

JIRA has an excellent API >> 

You can simply create your own extension using REST calls.

Highlighted
Occasional Contributor

Re: Is there a way to report the bug to JIRA on test failure through framework code. ??

I will giv this a try 🙂 Though I'm not an expert in JSON 😛

New Here?
Join us and watch the welcome video:
Announcements
Join TechCorner Challenge!
Want a fun and easy way to learn TestComplete? Try solving weekly TechCorner challenges and get into the Leaderboard!


Challenge Status

Compare images using the Region Checkpoint

See replies!

Converting UTC TimeDate in an Excel file

See replies!

Compare HTML table with Excel file and correct data in Excel file

Participate!

How to execute remote test and obtain results via Test Runner REST API

Participate!
Top Kudoed Authors