It happens very rarely that a functional test runs successfully on our local environment, but it fails on the Drupal CI Jenkins server. But sometimes it does. Fortunately, the CI server saves all the important output of the test run (log files, configurations), including the HTML files of the drupal pages visited during the Browser and Webdriver tests.

You can download the entire test artifact as well, but usually I only want to check the HTML output. This is how we can find and check these HTML files in the browser:

  1. Click the link of the test you want to check:

  2. Click on “View results on dispatcher”:

  3. Click “Build Artifacts”:

    From this point, you will browse the directories and the files of the test artifact.

  4. Click the “artifact” directory’s link:

  5. Select the task of which output you want to check. If the project uses the default build definition and the default drupalci.yml configuration, then the output of the Webdriver (aka FunctionalJavascript) tests can be found in the run_tests.js directory; every other PHPUnit test’s output will be in the run_tests.standard dir1. Pick the one you want to check:

  6. The HTML output we are usually looking for can be found in the simpletest_html directory.

There they are!

Happy coding!

Footnotes:

  1. These directory names are the same as the key of the corresponding job. ↩