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

testlink status not run with TAP and junit-xml

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • testlink-plugin
    • Jenkins ver. 2.32.2
      TestLink Plugin ver. 3.11
      TestLink ver. 1.9.16[DEV]

      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.

        1. JENKINS-41768.jpg
          JENKINS-41768.jpg
          194 kB

          [JENKINS-41768] testlink status not run with TAP and junit-xml

          Mark Crusher created issue -
          Mark Crusher made changes -
          Description Original: 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 comunicate on every build

          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}}

          any ideas? I spent few days and 32 runs of the job to get here and running out of ideas.           		New: 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

          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}}

          any ideas? I spent few days and 32 runs of the job to get here and running out of ideas.
          Mark Crusher made changes -
          Attachment New: JENKINS-41768.jpg [ 35802 ]
          Mark Crusher made changes -
          Attachment Original: JENKINS-41768.jpg [ 35802 ]
          Mark Crusher made changes -
          Attachment New: JENKINS-41768.jpg [ 35803 ]
          Mark Crusher made changes -
          Attachment Original: JENKINS-41768.jpg [ 35803 ]
          Mark Crusher made changes -
          Attachment New: JENKINS-41768.jpg [ 35805 ]
          Mark Crusher made changes -
          Description Original: 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

          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}}

          any ideas? I spent few days and 32 runs of the job to get here and running out of ideas.           		New: 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:
          {noformat}1..2
          not ok 1 - gui_arguments
          not ok 2 - gui_arguments{noformat}

          then the result shows this
          {noformat}Executing iterative Build Steps.

          Looking for the test results of TestLink test cases.

          Found 1 test result(s).

          Archiving artifacts
          Finished: SUCCESS{noformat}

          any ideas? I spent few days and 32 runs of the job to get here and running out of ideas.
          Mark Crusher made changes -
          Description Original: 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:
          {noformat}1..2
          not ok 1 - gui_arguments
          not ok 2 - gui_arguments{noformat}

          then the result shows this
          {noformat}Executing iterative Build Steps.

          Looking for the test results of TestLink test cases.

          Found 1 test result(s).

          Archiving artifacts
          Finished: SUCCESS{noformat}

          any ideas? I spent few days and 32 runs of the job to get here and running out of ideas.           		New: 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:
          {noformat}1..2
          not ok 1 - gui_arguments
          not ok 2 - gui_arguments{noformat}

          then the result shows this
          {noformat}Executing iterative Build Steps.

          Looking for the test results of TestLink test cases.

          Found 1 test result(s).

          Archiving artifacts
          Finished: SUCCESS{noformat}
          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.
          Mark Crusher made changes -
          Labels Original: tapResults New: results tapResults
          Mark Crusher made changes -
          Priority Original: Major [ 3 ] New: Blocker [ 1 ]

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

              Created:
              Updated: