0.17

Breaking change:

• revert to Gradle's default behaviour and publish HTML reports in reports/tests/task

New feature:

• support mixed modes where scalatest can be used alongside the existing Gradle test runners (thanks to @scr)

0.16

Breaking change in Gradle 4.0:

• Incompatibility with Gradle 4.0 - Test.getTestClassesDir() returns Java test classes only

0.15

Resolves incompatibility between Jacoco and ScalaTest when using the plugins dsl.

This does not occur when using the buildscript method of applying the plugin.

java.lang.instrument.IllegalClassFormatException: Error while instrumenting class

plugins {
    id 'jacoco'
    id 'com.github.maiflai.scalatest' version '0.14'
}

0.14

• isColorOutput has been removed in Gradle 3

0.13

• Better support for Gradle test logging
• Fixes missing class ConsoleRenderer when a test fails under Gradle 2.14.1

0.12

• Support configMap

0.11

• #26 - support Jacoco
• publish to the new gradle plugin repository

0.10

Minor fixes

• The I argument is ignored in Scalatest 2.0 (#23)
• Environment variables defined on the Test task are now propagated, e.g. the following should work as expected:

test {
  environment 'a', 'b'
}

0.9

Suites

Suites are supported with another extension to the Test task.

task userStories(type: Test) {
    suite 'com.example.UserStories'
    // suites 'a.Spec', 'b.Spec', 'etc'
}

Reporting

New Test tasks are now configured to have an HTML report directory based on their task name. This means that they should not overwrite the reports of sibling tasks.

It may mean that existing manual configuration can be removed.

Support --tests filtering

0.8

support gradle-style test filtering using the scalatest -z simplified…