Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41768

testlink status not run with TAP and junit-xml

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      when trying to execute test case job in Jenkins using TAP I will always see Testlink result as 'Not run' but build number variable is sent to testlink to create a new build there, so they know about each other and communicate on every build
      colored text
      perhaps my implementation of TAP file format/name is wrong?
      file name: gui_arguments
      content:

      1..2
      not ok 1 - gui_arguments
      not ok 2 - gui_arguments

      then the result shows this

      Executing iterative Build Steps.
      
      Looking for the test results of TestLink test cases.
      
      Found 1 test result(s).
      
      Archiving artifacts
      Finished: SUCCESS

      but status results are always like this:
      TestLink build ID: 3

      TestLink build name: 0.10

      Total of 1 tests. Where 0 passed, 0 failed, 0 were blocked and 1 were not executed.

      List of test cases and execution result status

      Test case ID Test case external ID Version Name Test project ID Execution status
      1113 OTC-31 1 automatic test test 1 Not Run

      any ideas? I spent few days and 32 runs of the job to get here and running out of ideas.

        Attachments

          Activity

          Hide
          nescius Mark Crusher added a comment - - edited

          I am starting to like the TAP format, which I still dont comprehend is the documentation

          This is the custom field used by the plug-in to link a test case in TestLink with your test results. This custom
          field must exist in the list of custom fields.

          could this be extended just a little? does it have to have a value same to tap thing? eg. one
          testlink test case contain custom field bar = foo, other one with bar=fuuu
          then the tap would look like this?

          TAP version 13
          1..3
          ok 1 - fuuu # bar
            ---
            message: 'Hello World'
            severity: fail
            ...
          ok 2 - foo # bar
            ---
            message: 'Hello World'
            severity: fail
            ...

          well, i tried that (among many other things) with no success.

          Show
          nescius Mark Crusher added a comment - - edited I am starting to like the TAP format, which I still dont comprehend is the documentation This is the custom field used by the plug-in to link a test case in TestLink with your test results. This custom field must exist in the list of custom fields. could this be extended just a little? does it have to have a value same to tap thing? eg. one testlink test case contain custom field bar = foo, other one with bar=fuuu then the tap would look like this? TAP version 13 1..3 ok 1 - fuuu # bar --- message: 'Hello World' severity: fail ... ok 2 - foo # bar --- message: 'Hello World' severity: fail ... well, i tried that (among many other things) with no success.
          Hide
          nescius Mark Crusher added a comment -

          I also tried to implement my own junit-xml output with same results

          Show
          nescius Mark Crusher added a comment - I also tried to implement my own junit-xml output with same results

            People

            • Assignee:
              kinow Bruno P. Kinoshita
              Reporter:
              nescius Mark Crusher
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: