gurock / trcli

TR CLI (trcli) is a command line tool for interacting with TestRail.
Mozilla Public License 2.0
48 stars 39 forks source link

jUnit import testsuite/testsuites properties #196

Open janholusa opened 5 months ago

janholusa commented 5 months ago

TestRail CLI Version

1.6.1

CLI Environment

debian

TestRail Version

8.0.3 Default (3063)Built on

TestRail Instance Type

Enterprise Cloud

Current behavior

Currently each testsuite property is displayed in testrun description. Also properties under for testsuites attribute are ignored: image

imported file

<testsuites name="Autotest test" time="1882.579">
 <properties>
    <property name="prop-top" value="val-top"/>
 </properties>

 <testsuite name="9 Setup: Setup Device Context" time="13.934" tests="5" failures="0" errors="0" skipped="0" file="SetupDeviceContext.php">
    <properties>
      <property name="prop1" value="val1"/>
    </properties>
    <testcase name="53" classname="a" time="10.358" file="tests/tests/Unifi/SetupDeviceContext.php" line="27">
      <properties>
        <property name="testrail_result_field" value="status_id:1"/>
      </properties>
    </testcase>
  </testsuite>

  <testsuite name="10 Setup: Setup Device Context" time="13.934" tests="5" failures="0" errors="0" skipped="0" file="SetupDeviceContext.php">
   <properties>
      <property name="setting2" value="value2"/>
    </properties>
    <testcase name="58" classname="e" time="0.102" file="SetupDeviceContext.php" line="76">
      <properties>
        <property name="testrail_result_field" value="status_id:1"/>
      </properties>
    </testcase>

  </testsuite>
</testsuites>

Btw it works as documented here: https://support.testrail.com/hc/en-us/articles/12989737200276-JUnit-to-TestRail-mapping#h_01H9QJ39FJ76KWJFEBDPMD3XC2

Desired behavior

I would expect that "parameters" under testsuite section will be displayed under group name

And parameters in testsuites section will be displayed in TR description (where are currently displayed all parameters from testsuite sections in whole testrun)

More Details

No response

bitcoder commented 5 months ago

Hi, so from my understanding, currently it works as documented right? You wanted it to behave differently from the current documented behaviour, correct?

janholusa commented 5 months ago

@bitcoder well, yes. In this meaning, it might be considered as improvement - not a bug.

I mean - there is missing option to make suite description from junit file (talking about creating testcases automatically).