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

Boost test schema wrongfully rejects testsuite-scope exceptions

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • xunit-plugin
    • None

      If an exception gets thrown as part of constructing a fixture, the Exception tag appears directly within TestSuite.

      The schema defined by xunit-plugin only allows that at the TestCase level, which is wrong.

          [JENKINS-61115] Boost test schema wrongfully rejects testsuite-scope exceptions

          Mathias Gaunard created issue -

          Nikolas Falco added a comment -

          Which version of tools are you using? Could you attach the report file?

          Nikolas Falco added a comment - Which version of tools are you using? Could you attach the report file?

          Mathias Gaunard added a comment -

          The bug is still present in HEAD.

          https://github.com/jenkinsci/xunit-plugin/blob/cbc073cf75b398d278a159c5819970781c3ef12b/src/main/resources/org/jenkinsci/plugins/xunit/types/boosttest-1.5.0.xsd#L155

          Clearly the choice here is missing a bunch of options?

          I cannot freely share real testcases, but as I described it's trivial to produce one. <TestSuite name="foo"><Exception>FooException</Exception></TestSuite> should do I suppose?

          Mathias Gaunard added a comment - The bug is still present in HEAD. https://github.com/jenkinsci/xunit-plugin/blob/cbc073cf75b398d278a159c5819970781c3ef12b/src/main/resources/org/jenkinsci/plugins/xunit/types/boosttest-1.5.0.xsd#L155 Clearly the choice here is missing a bunch of options? I cannot freely share real testcases, but as I described it's trivial to produce one. <TestSuite name="foo"><Exception>FooException</Exception></TestSuite> should do I suppose?

          Nikolas Falco added a comment -

          Could you share the generated report? You can replae you company package/file path with other one (com.acme....)

          Nikolas Falco added a comment - Could you share the generated report? You can replae you company package/file path with other one (com.acme....)

          Mathias Gaunard added a comment -

          I already gave an example above.

          I have also done a pull request if that helps: https://github.com/jenkinsci/xunit-plugin/pull/83

          Mathias Gaunard added a comment - I already gave an example above. I have also done a pull request if that helps:  https://github.com/jenkinsci/xunit-plugin/pull/83

          Nikolas Falco added a comment -

          You can create an ad hoc cpp test case to that produce the report like you have.

          mgaunard: <TestSuite name="foo"><Exception>FooException</Exception></TestSuite> should do I suppose?

          I would not suppose, Something generated by the tool is used to also map testsuite exception by XSLT

          Nikolas Falco added a comment - You can create an ad hoc cpp test case to that produce the report like you have. mgaunard : <TestSuite name="foo"><Exception>FooException</Exception></TestSuite> should do I suppose? I would not suppose, Something generated by the tool is used to also map testsuite exception by XSLT
          Nikolas Falco made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            nfalco Nikolas Falco
            mgaunard Mathias Gaunard
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: