Highlights of this release

Update from ScalaWebTest <= 1.0.3

We changed the artifact ids, for better autocompletion in your IDE. Therefore you have to change the artifact id in your dependencies. Just add the prefix scalawebtest- to all your dependencies. For example, change 

            libraryDependencies += "org.scalawebtest" %% "core" % "1.0.3" % "it"
to 
            libraryDependencies += "org.scalawebtest" %% "scalawebtest-core" % "1.0.4" % "it"
Or in a maven project from 
            <dependency>
                <groupId>org.scalawebtest</groupId>
                <artifactId>core_2.11</artifactId>
                <version>1.0.3</version>
                <scope>test</scope>
            </dependency>
to 
            <dependency>
                <groupId>org.scalawebtest</groupId>
                <artifactId>scalawebtest-core_2.11</artifactId>
                <version>1.0.4</version>
                <scope>test</scope>
            </dependency>
You might change from core_2.11 to scalawebtest-core_2.12, in case you want to upgrade from Scala 2.11 to 2.12 aswell.

ScalaWebTest now supports all relevant Scala versions

ScalaWebTest now supports Scala 2.12, 2.11 and 2.10. Our Scala cross version build uses Scala 2.12.0, 2.11.8 and 2.10.6. If you start a new project or introduce Scala in to your project, we recommend to use 2.12. If you introduce ScalaWebTest into an AEM (Adobe Experience Manager) project, we recommend to stay on 2.11 because the PageProperties trait is not available with 2.12 yet, as it depends on play-json, which isn't released for 2.12 yet.

We introduced a new feature in the AEM module

You can add the new trait PageProperties to your test, to get the field pageProperties populated with a JsValue, which represents the properties of the current page. For further details read the documentation to the PageProperties trait.