Stryker4s v0.2.1

We just released Stryker4s v0.2.1! This marks our second release thusfar. It's mostly focused on fixing bugs, providing a stable environment and supporting more types of projects. Give it a try by adding the sbt plugin to your project:

addSbtPlugin("io.stryker-mutator" % "sbt-stryker4s" % "0.2.1")

Features

• Our releases are now automated by sbt-ci-release. We'll also be releasing more often (#131).
  • Every commit that is merged into master will now become a SNAPSHOT release. Check out the documentation for more info.
• A warning is now logged when Stryker4s is ran with the default JVM memory settings. Mutation testing is a taxing process, and increasing the memory can halt the process to a grind (#139).
• Logging is improved for when no mutations are found (#140).

Bug fixes

• We've fixed some bugs related to generating mutated code. If you ran into problems with the previous release, please try again (#126, #130, #147)!
• Fixed a bug bug where files that were deleted, but not yet staged on git would throw a FileNotFoundException was fixed (#134).
• The sbt plugin now properly copies over any JVM system properties that are set (#136).

Other changes

• The submodules have been re-organized. This means stryker4s-util is removed, and most plugins/runners only depend on stryker4s-core now. The command-runner is now also in a separate package (#128).
  • A nice side-effect of this is that the command-runner is now easily runnable via Coursier. Simply run coursier launch --scaladex stryker4s-command-runner to start mutation testing a project that does yet have a plugin!
• We now test against multiple JDK's on Travis. This should help us catch any future compatibility problems with different JVM's (#129).
• The sbt plugin has had a slight refactoring to clean it up and only apply some settings once (#138).
• Some documentation was added detailing our versioning strategy (#107).
• Generated mutated code is now slightly cleaner (#144).