Highlights of this release

Update from ScalaWebTest <= 1.1.1

The version bump to 2.0.0 isn't because of big changes, but because we start to use semantic versioning. More on this topic in the release highlights.

We updated most of our dependencies and suggest you update them in your project as well, in case you manage any of our transitive dependencies explicitly in your project. If you build your project with maven, we suggest you use our bill-of-materials, which automatically takes care of version updates of our dependencies. See Add ScalaWebTest to your maven project If you build your project with sbt, we suggest you copy our most important transitive dependencies from the Add ScalaWebTest to your sbt project section.

Introduction of semantic versioning

As of release 2.0.0 ScalaWebTest is committed to use semantic versioning as described in http://semver.org/spec/v2.0.0.html

Given a version number MAJOR.MINOR.PATCH, increment the:
  1. MAJOR version when you make incompatible API changes,
  2. MINOR version when you add functionality in a backwards-compatible manner, and
  3. PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

A version bump to 2.0.0 was required to introduce semantic versioning, because version 1.0.4 introduced some incompatible API changes. ScalaWebTest now uses MigrationManager to make sure no incompatible changes slip the versioning scheme.

Using github milestones

We use github milestones now to bundle all issues, which where solved with a specific version of ScalaWebTest. Release 2.0.0 is our first milestone.

Consistent behavior between verifying complete documents and part of the DOM

Thanks to Issue 47 the behavior of fits and doesntFit, when used to verify parts of the DOM, is now consistent with the behavior when verifying complete documents.