The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

JUnit Realtime Test Reporter Plugin

View this plugin on the Plugins site

realtimeJUnit: Display JUnit test results as they appear

Runs a block and archives JUnit results at the end, exactly like the junit step would. The difference is that test results are displayed as they appear.
  • testResults : String
  • allowEmptyResults : boolean (optional)
  • healthScaleFactor : double (optional)
  • keepLongStdio : boolean (optional)
  • parseInterval : long (optional)

    The interval between two file system scans to parse test results (in seconds). Must be a positive value greater than 0. Default value is calculated as 1/100 of the estimated build duration, but never more often than every 5 seconds.

  • skipMarkingBuildUnstable : boolean (optional)
  • testDataPublishers (optional)
      Array / List of Nested Choice of Objects
    • attachments
      • $class: 'AutomateTestDataPublisher'
        • $class: 'ClaimTestDataPublisher'
          • $class: 'JUnitFlakyTestDataPublisher'
            • $class: 'JunitResultPublisher'
              If checked, each JUnit test result XML file will be examined to see if it represents a SOASTA CloudTest composition. For applicable tests, a hyperlink to the SOASTA CloudTest dashboard will be inserted into the test report.
              • urlOverride : String
                Specify the CloudTest URL to use when creating hyperlinks to CloudTest dashboards. Normally, this can be left blank, and the URL will be extracted from the test result file.
            • $class: 'PerfSigTestDataPublisher'
              • dynatraceProfile : String
            • $class: 'SahaginTestDataPublishser'
              • $class: 'SauceOnDemandReportPublisher'
                Show embedded Sauce OnDemand reports, including video and logs. Your test should use Selenium client factory (at least version 1.3 to match test cases to individual Sauce OnDemand jobs).
                • jobVisibility : String (optional)
                  Set your test results visibility permissions. The Sauce Documentation has all the various levels described in detail.
              • $class: 'StabilityTestDataPublisher'
                • $class: 'TestCafePublisher'
                  • $class: 'TestReporter'
                    • $class: 'YoutrackTestDataPublisher'

                    Was this page helpful?

                    Please submit your feedback about this page through this quick form.

                    Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

                        


                    See existing feedback here.