This maven plugin is designed to take tests results produced by continuous integration and publish them to github as a "check" annotation on a particular commit. For the full instructions about how to get this working, see the Test Check Publisher Github application.

• The source code be found on the git repository.
• Maven packages are published via
• Documentation:

You need to add the test-check-publisher integration to your repository and then add something like the following to your pom.xml file in the build, plugins section:

<plugin>
	<groupId>com.j256.testcheckpublisher</groupId>
	<artifactId>test-check-publisher-maven-plugin</artifactId>
	<version>1.5</version>
</plugin>

After you have run your unit tests, you need to execute:

mvn test-check-publisher:publish

Here are some examples of output from github:

• Simulated errors

Right now the plugin is pretty limited to Java/surefire results but the system has been built to be more generic. If you have a testing framework that you'd like it to support, please add an issue. All that is required is the reading in test results and posting something like the following JSON entity to the server.

{
  "magic": 237347409389423823,
  "owner": "owner",
  "repository": "repo",
  "commitSha": "sha",
  "secret": "secret env value from installation",
  "results": {
    "name": "Test results name",
    "numTests": 10,
    "numFailures": 1,
    "numErrors": 2,
    "numSkipped": 0,
    "fileResults": [
      {
        "path": "path/to/file1.java",
        "startLineNumber": 101,
        "endLineNumber": 101,
        "testLevel": "ERROR",
        "timeSeconds": 0.1,
        "testName": "testName",
        "message": "assert error",
        "details": "more details here"
      }
    ],
  }
}

The following image shows an example of the output that you would see on Github associated with a particular commit. This could provide more information if your Continuous Integration run failed because of a unit test issue.

The maven plugin supports a couple of configuration parameters:

<plugin>
	<groupId>com.j256.testcheckpublisher</groupId>
	<artifactId>test-check-publisher-maven-plugin</artifactId>
	<configuration>
		<field>value</field>
	</configuration>
</plugin>

In the configuration for the plugin, you can specify a comma separated list of tokens which affect the resulting check annotations and details formatting.

The following tokens are supported:

There are two different checks output sections. Closer to the top of the page is a details section which is used to provide details of the check in markdown. Below it is the annotations section where file and line-number is annotated with the results of a test. The problem is that not all of the files and line-numbers are shown in the commit. You might make a change to your code and fail a test that hasn't been touched in months and the annotation will look good but the link to the file/line will be broken. The server tries to detect this and writes some of the results into the details section and some into the annotations based on whether or not it was involved in the commit. It's not perfect.

If you want all of your test results in the annotations section then you should use the nodetails token. If you think that the details looks good, you might try noannotate. If you want to see the passing tests as well in the details section then you might want to add alldetails.