Sribala's avatar
Sribala
New Member
7 years ago
Status:
Selected for Development

Need actual Junit reports to be generated and not Just Junit Style reports

Hi,

Jenkins and Test Complete Integration produces just 'Junit Style Reports' but not the actual 'Junit report'.  Since this is not an actual 'Junit Report', this format is not being accepted while posting the report in our system.

 

Here are the examples of Junit Style Report and actual Junit Report

 

Junit Style Report- Result from Jenkins-TestComplete integration:
<?xml version='1.0' encoding='UTF-8'?>
<result plugin="junit@1.20">
<suites>
<suite>
<file>C:\Jenkins\jobs\Test\builds\51\tcreports\8023278.xml</file>
<name>ETR</name>
<duration>47.851</duration>
<timestamp>2017-08-01T06:33:49.972-04:00</timestamp>
<time>47.85100173950195</time>
<cases>
<case>
<duration>47.851</duration>
<className>ETR.ETR</className>
<testName>ProjectTestItem1</testName>
<skipped>false</skipped>
<failedSince>0</failedSince>
</case>
</cases>
</suite>
</suites>
<duration>47.851</duration>
<keepLongStdio>true</keepLongStdio>
</result>

 

Actual Junit report:
<?xml version="1.0" encoding="UTF-8" ?>
<testsuites id="20140612_170519" name="New_configuration (14/06/12 17:05:19)" tests="225" failures="1262" time="0.001">
<testsuite id="codereview.cobol.analysisProvider" name="COBOL Code Review" tests="45" failures="17" time="0.001">
<testcase id="codereview.cobol.rules.ProgramIdRule" name="Use a program name that matches the source file name" time="0.001">
<failure message="PROGRAM.cbl:2 Use a program name that matches the source file name" type="WARNING">
WARNING: Use a program name that matches the source file name
Category: COBOL Code Review – Naming Conventions
File: /project/PROGRAM.cbl
Line: 2
</failure>
</testcase>
</testsuite>
</testsuites>

7 Comments

Sort By
  • IFERNANDEZ's avatar
    IFERNANDEZ
    Occasional Contributor
    7 years ago

    Hi.

    I'm stuck exactly at the same point.

    You're getting the actual /api/xml results produced by Jenkins. But they're not Junit - style. So you need to parse them.

    Which actually is not that simple. Unfortunately.

    This affects result publishing, Testlink... A real disaster from Smartbear / Testcomplete integration with Jenkins.

  • kamal-a's avatar
    kamal-a
    Senior Member
    6 years ago

    This new feature would be usefull for me too. Is there any news about it?

  • flying_sqa's avatar
    flying_sqa
    New Member
    6 years ago

    It is nice to see that this request was 'Selected for Development' but please don't just put the new functionality in a Jenkins plugin, it needs to be available as core functionality from Test Complete and Test Execute. My CI is TeamCity which doesn't even have an integration with Test Complete/Execute, so you'll be doing me no favors if you just add the JUnit XML feature to Jenkins!

  • prashantmohan's avatar
    prashantmohan
    Staff
    6 years ago

    Yes! You'll be able to export as JUnit right from TestComplete, independent of Jenkins.