-
Updated
Oct 16, 2020 - JavaScript
mutation-testing
Here are 156 public repositories matching this topic...
-
Updated
Oct 17, 2020 - TypeScript
-
Updated
Oct 19, 2020 - Ruby
-
Updated
Oct 19, 2020 - PHP
-
Updated
Dec 31, 2017 - PHP
-
Updated
Oct 19, 2020 - Java
-
Updated
Oct 14, 2020 - C++
Is your feature request related to a problem? Please describe.
I'm not being able to run Stryker in a project (netframework 4.5) inside a machine that doesn't have VS2017 installed (it has VS2015). Stryker fails when it tries to build the solution.
I ran some tests and found out that it tries to use the MSBuild.exe located at the first path defined on MSBuildHelper's.fallbackLocations.
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
Oct 17, 2020 - Swift
-
Updated
Jul 4, 2020 - Python
-
Updated
Aug 21, 2020
-
Updated
Oct 15, 2020 - Groovy
-
Updated
Sep 11, 2020 - TypeScript
Summary
At the start of the program, I see the following output:
15:17:59.096 [pool-49-thread-1] INFO stryker4s.mutants.Mutator - Found 12 of 14 file(s) to be mutated.
15:17:59.097 [pool-49-thread-1] INFO stryker4s.mutants.Mutator - 257 Mutant(s) generated.
15:17:59.473 [scala-execution-context-global-367] INFO stryker4s.sbt.runner.SbtMutantRunner - Setting up mutated environme
ETA Calculator
-
Updated
Aug 23, 2020 - Ruby
-
Updated
Oct 16, 2020 - Java
-
Updated
Feb 27, 2020 - C#
-
Updated
Mar 29, 2020 - Haskell
-
Updated
Aug 18, 2020 - Groovy
-
Updated
Oct 13, 2020
-
Updated
Jan 17, 2020 - Python
-
Updated
Jun 21, 2020 - Crystal
-
Updated
Oct 19, 2020 - D
-
Updated
Jun 27, 2020 - Java
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."
Currently, the log in the database does not contain any information about the runtime of the individual job_ids. But I think this could be quite an interesting information to have.
The runtime can be logged either as a duration or with two timestamps:
start_jobandend_job.