Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spike use of a mutation testing framework. #58

Open
sageserpent-open opened this issue Apr 6, 2019 · 2 comments
Open

Spike use of a mutation testing framework. #58

sageserpent-open opened this issue Apr 6, 2019 · 2 comments

Comments

@sageserpent-open
Copy link
Owner

sageserpent-open commented Apr 6, 2019

Evaluate Stryker4s and ScalaMu.

@sageserpent-open
Copy link
Owner Author

sageserpent-open commented Apr 6, 2019

The motivation behind this is driven by the need to keep adjusting the extent to which Scalacheck hammers the various test suites, especially the world specifications. When these test were written, a lot of manual fault injection was performed to verify that they really did test effctively. However, I have become concerned that the recent repeated turning down of the dials to placate Travis may have made these tests ineffective at detecting faults, so mutation testing would be a nice blanket approach to checking this.

@sageserpent-open
Copy link
Owner Author

Did some experimenting with Stryker4s on 'BlobStorageImplementation' and found it quite effective. Some patching of the sources was required (eta-expansions) to get it building with Stryker4s; nevertheless that tool is worth investigating further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant