Skip to content

Releases: stryker-mutator/stryker4s

v0.17.1

15 Mar 11:59
ffe3235
Compare
Choose a tag to compare

0.17.1 (2025-03-15)

Bug Fixes

  • handle relative paths correctly when fixing compile errors (#1731) (c341c20)

v0.17.0

14 Mar 17:11
c44f0d2
Compare
Choose a tag to compare

0.17.0 (2025-03-14)

Features

Bug Fixes

  • compatibility with sbt-crossproject (#1648) (3879b63)
  • disable fatal-warnings scalacOption when mutating (#1680) (0b1db17)
  • handle relative and absolute base-dir paths (#1725) (f357940)
  • handle WSL correctly when opening report (#1726) (f2a79e5)
  • mutate glob (a933e7b)
  • sbt: glob expressions for mutate and files on windows (#1727) (2901f08)

v0.16.1

18 Apr 13:40
fbdcba5
Compare
Choose a tag to compare

0.16.1 (2024-04-18)

This release updates Scalameta to 4.9.3, resolving an issue some users might have when another plugin is also using a recent version of Scalameta.

v0.16.0

27 Dec 12:57
a0639ac
Compare
Choose a tag to compare

0.16.0 (2023-12-27)

This release mainly features improved reporting. The biggest feature is inclusion of tests in the report. Stryker4s will now show all your test suites, and (if supported) the individual tests of each test suite. This makes it easier to see which tests cause failing mutants.

Test output

In the HTML report, a new tab is added to show the test results:

image

Opening a test suite reveals the tests inside that suite, clicking on one shows more information available about what mutants it covers and might have killed:

image

Back on the mutant tab, each mutant will now show what tests are covered by it. And for killed mutants the test exception output is shown:

image

Regex mutations

Regex mutations now show the precise characters inside the expression that has been mutated as its location, and a richer description with info about the mutation is added:

image
image

image

⚠ BREAKING CHANGES

  • up minimum-supported sbt version to 1.7.0 (#1476)

Features

  • add weapon-regex description to mutant and improve statusReason report field (#1470) (bb8878f)
  • regex: use correct replacement and location from weapon-regex mutations (#1480) (fc9854b)
  • report: add tests and coverage per-test to report (#1475) (5a529c8)

Bug Fixes

Miscellaneous Chores

Stryker4s v0.15.2

16 Nov 15:02
73533c8
Compare
Choose a tag to compare

🐛 Bugfixes

Stryker4s v0.15.1

14 Nov 10:57
Compare
Choose a tag to compare

This patch release mostly refactors some internal module layout.

For Maven users, the default files to mutate configuration now uses Maven project info. For sbt users, using a snapshot release of the plugin will no longer require also adding a snapshot resolver to your project too (it is done automatically now).

🐛 Bugfixes

🧰 Maintenance

Stryker4s v0.15.0

18 Oct 20:42
9a18b44
Compare
Choose a tag to compare

See https://stryker-mutator.io/blog/stryker4s-0-15-is-here/

🚀 Features

🐛 Bugfixes

🧰 Maintenance

📖 Documentation

Stryker4s v0.14.3

03 Jan 16:34
v0.14.3
4d65113
Compare
Choose a tag to compare

🚀 Features

🧰 Maintenance

Stryker4s v0.14.2

13 Dec 20:59
v0.14.2
7ba6a0d
Compare
Choose a tag to compare

This release updates log4j to 2.16.0 for the command-runner to fix the security issue. If you use the sbt or Maven plugin, this has no impact as those plugins do not use log4j. If you use the command-runner, upgrading is recommended.

Also updates the HTML report to a newer version with some performance fixes and a new 'diff' view #1028:

html report diff view

🧰 Maintenance

Stryker4s v0.14.1

01 Nov 20:57
v0.14.1
350ca90
Compare
Choose a tag to compare

Stryker4s is a mutation testing framework. It tests your tests by temporarily inserting small bugs, or mutants, into your production code. Your tests are run for each mutant. If your tests fail, then the mutant is killed. If your tests passed, the mutant survived. The higher the percentage of mutants killed, the more effective your tests are. See the website for more information.

This release adds per-test coverage. That means when testing a mutant, Stryker4s will only run the tests that cover that mutant, instead of all tests. Tests that don't cover a mutant can never kill it. Makes sense, right? That's why we added it. When running Stryker4s on Stryker4s, this improved the performance by about 40% 🥳! Big thanks to @OssamaSijbesma for adding this feature!

🚀 Features

🧰 Maintenance