-
Updated
Mar 6, 2022 - JavaScript
mutation-testing
Here are 199 public repositories matching this topic...
-
Updated
Mar 15, 2022 - TypeScript
-
Updated
Feb 18, 2022 - Ruby
-
Updated
Mar 20, 2022 - PHP
-
Updated
Mar 22, 2022 - Java
-
Updated
Mar 21, 2022 - C#
-
Updated
Dec 31, 2017 - PHP
-
Updated
Mar 17, 2022 - C++
The plugin source is currently split into two files, one of which is auto-generated by build.rs
. The lib.rs
is getting unwieldy. Time to browse for sets of functionality that can be put into their own modules, before navigating the source gets too cumbersome.
Document mutations
-
Updated
Nov 5, 2021 - Swift
-
Updated
Nov 6, 2021 - Python
-
Updated
May 13, 2021
-
Updated
Mar 13, 2022 - Groovy
-
Updated
Dec 31, 2021 - TypeScript
Right now the temp dir is deleted after running using a FS2 tempDir Resource
. This is done in the MutantRunner.
It'd be nice to have a config option to keep the generated temp dir after running for debugging purposes to look
-
Updated
Dec 19, 2021 - Java
-
Updated
Mar 11, 2022 - Python
-
Updated
Aug 23, 2020 - Ruby
It would sometimes be useful to check for mutants in just one or a few files, e.g.
cargo mutants -f mutate.rs
Probably this should match a whole path from the root if it contains slashes, and just the filename if it does not.
-
Updated
Dec 3, 2021 - Haskell
-
Updated
Mar 23, 2021 - C#
-
Updated
Mar 22, 2022 - C
-
Updated
Jan 31, 2022 - Groovy
-
Updated
Mar 14, 2022
-
Updated
Dec 11, 2021 - Crystal
Improve this page
Add a description, image, and links to the mutation-testing topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the mutation-testing topic, visit your repo's landing page and select "manage topics."
Right now the sphinx-apidoc results are part of the repo, but there's no real reason for that. We should be able to generate those docs on demand whenever we build the sphinx project.