mutalk

mutalk copied to clipboard

Ignore halts

2

If any test arrives at a `halt` during the mutation, then the debugger is open (and stops the analysis until proceed). I would like to interpret this as a fail...

PalumboN

Maybe tell the user which test failed

DurieuxPol

The Heatmap matrix introduced in here https://github.com/pharo-contributions/mutalk/pull/79 uses a linear palette of colors. This means that low values such as 0 and 1 get very similar colors. However, 0 and...

guillep

```smalltalk nodeToMutate | n searcher | n := 1. searcher := RBParseTreeSearcher new matches: operator expressionToReplace do: [ :node :answer | n = nodeNumber ifTrue: [ ^ node ]. n...

DurieuxPol

Some tests may need to be reviewed and refactored, like in `AllTestsMethodsRunningTestSelectionStrategyTest`, `MutationTestingAnalysisTest` or `MutationTestingAnalysisBuilderTest`.

DurieuxPol

Github Actions integration

1

Hi there, I would like to integrate Mutalk into Github actions, so all projects can easily benefit from mutation testing by simply adding a [workflow file](https://github.com/pavel-krivanek/mutalk/blob/mutalkCI/workflow/mutalkCI.yml). I create this thread...

mabdi

Some tests are broken in Pharo 9 because Microdown is not readily available there. _Originally posted by @guillep in https://github.com/pharo-contributions/mutalk/issues/118#issuecomment-2194847527_

guillep