• Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • analysis-model
    • None

      With packages like jest-junit. it's possible to generate a .xml file for tests or lint overviews, similar to ESLint's "-f checkstyle" option.

      ESLint has a dedicated sidebar button, icon and view. It would be nice to have the same for jest.

          [JENKINS-68967] Support for jest junit reports

          Ulli Hafner added a comment -

          But these are test results. Shouldn't those be better shown in a test view? The warnings plugin cares about warnings. How do you want to map the results to warnings?

          Ulli Hafner added a comment - But these are test results. Shouldn't those be better shown in a test view? The warnings plugin cares about warnings. How do you want to map the results to warnings?

          Alexander Brandes added a comment - - edited

          Yeah, this may be something for analysis model then, I guess? At least jest is for JS's jest junit one, a test overview makes more sense here.

          I was under the impression, that warnings ng provides the logic, but it seems to be coming from analysis model.

          Alexander Brandes added a comment - - edited Yeah, this may be something for analysis model then, I guess? At least jest is for JS's jest junit one, a test overview makes more sense here. I was under the impression, that warnings ng provides the logic, but it seems to be coming from analysis model.

          Ulli Hafner added a comment -

          analysis-model provides the model and the report parsers, the warnings plugin contains the UI integration into Jenkins.

          But both care about warnings and not test results. So what I mean: why don't you integrate the jest results into the JUnit plugin, that should be more suitable? The test model is much simpler than the warnings model.

          Ulli Hafner added a comment - analysis-model provides the model and the report parsers, the warnings plugin contains the UI integration into Jenkins. But both care about warnings and not test results. So what I mean: why don't you integrate the jest results into the JUnit plugin, that should be more suitable? The test model is much simpler than the warnings model.

          Ulli Hafner added a comment -

          As mentioned above, Jest (https://github.com/jest-community/jest-junit) is for unit tests and not warnings.

          Ulli Hafner added a comment - As mentioned above, Jest ( https://github.com/jest-community/jest-junit ) is for unit tests and not warnings.

            drulli Ulli Hafner
            notmyfault Alexander Brandes
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: