Jenkins中JUnit插件未展示全部测试结果问题求助

Let's break down the possible issues and fix them step by step:

1. Check Test Report Path Configuration #

First, verify if Jenkins is actually looking for all your XML files. Go to your Jenkins job configuration, find the Publish JUnit test result report section, and check the Test report XMLs field:

• If you're using a pattern like **/TEST-*.xml, it might only pick up JUnit's default-named reports, but miss the ones generated by Protractor.
• Fix this by using a broader pattern like **/*.xml to include all XML files in subdirectories, or explicitly list both patterns separated by commas: **/TEST-*.xml,**/protractor-*.xml (adjust the Protractor file prefix to match your actual output).

2. Validate XML Format Compatibility #

Jenkins' JUnit plugin expects XML files to follow the standard JUnit report structure. The jasmine-junit-xml-reporter might generate files with minor differences that the plugin can't parse properly:

• Manually open one of your Protractor-generated XML files and compare it with a working JUnit XML file. Look for missing standard tags like <testsuite>, <testcase>, or non-standard attributes that might throw off the parser.
• Tweak your Protractor reporter configuration to generate more JUnit-compliant output. For example, enable consolidated reports (single XML file instead of multiple) which are often easier for Jenkins to process:

  const jasmineReporters = require('jasmine-reporters');
  jasmine.getEnv().addReporter(new jasmineReporters.JUnitXmlReporter({
      savePath: './your-report-dir',
      consolidateAll: true,
      filePrefix: 'protractor-test-results'
  }));
  

3. Verify File Permissions & Generation Timing #

• Permissions: Ensure the Jenkins user has read access to all XML files. Add a build step (like ls -l ./your-report-dir on Linux or dir your-report-dir on Windows) to check file owners and permissions. If the files are owned by a different user, adjust permissions with chmod or run your test commands as the Jenkins user.
• Timing: Make sure your Protractor tests finish writing the XML files before Jenkins runs the JUnit report publisher. If you're using a pipeline, ensure the Protractor stage runs synchronously (no background processes). For freestyle jobs, confirm the Protractor build step is placed before the JUnit report publishing step.

4. Update Jenkins JUnit Plugin #

Outdated versions of the JUnit plugin might have bugs or limited support for third-party XML reports. Go to Manage Jenkins > Plugins and check if there's an update available for the JUnit plugin. Install the latest version and re-run your job.

If none of these steps work, check Jenkins' build logs for any errors related to parsing XML files—often the plugin will log warnings or errors when it can't process a report.

内容的提问来源于stack exchange，提问作者learner