Added documentation on new option (and tweaked the rest)

Author: toote

README.md

@@ -30,37 +30,42 @@ Example: `tmp/junit-*.xml`
 
 Forces the creation of the annotation even when no failures or errors are found
 
+### `context` (optional)
+
+Default: `junit`
+
+The buildkite annotation context to use. Useful to differentiate multiple runs of this plugin in a single pipeline.
+
 ### `job-uuid-file-pattern` (optional)
+
 Default: `-(.*).xml`
 
-The regular expression (with capture group) that matches the job UUID in the junit file names. This is used to create the job links in the annotation.
+The regular expression (with capture group) that matches the job UUID in the junit file names. This is used to create the job links in the annotation. 
 
 To use this, configure your test reporter to embed the `$BUILDKITE_JOB_ID` environment variable into your junit file names. For example `"junit-buildkite-job-$BUILDKITE_JOB_ID.xml"`.
 
 ### `failure-format` (optional)
-Default: `classname`
 
 This setting controls the format of your failed test in the main annotation summary.
 
 There are two options for this:
-* `classname`
+* `classname` (the default)
   * displays: `MyClass::UnderTest text of the failed expectation in path.to.my_class.under_test`
 * `file`
   * displays: `MyClass::UnderTest text of the failed expectation in path/to/my_class/under_test.file_ext`
 
 ### `fail-build-on-error` (optional)  
+
 Default: `false`
 
-If this setting is true and any errors are found in the JUnit XML files during
-parsing, the annotation step will exit with a non-zero value, which should cause 
-the build to fail.
+If this setting is true and any errors are found in the JUnit XML files during parsing, the annotation step will exit with a non-zero value, which should cause the build to fail.
 
-### `context` (optional)
-Default: `junit`
+### `min-tests` (optional, integer)
 
-The buildkite annotation context to use. Useful to differentiate multiple runs of this plugin in a single pipeline.
+Minimum amount of run tests that need to be analyzed or a failure will be reported. It is useful to ensure that tests are actually run and report files to analyze do contain information.
 
 ### `report-slowest` (optional)
+
 Default: `0`
 
 Include the specified number of slowest tests in the annotation. The annotation will always be shown.