Benjamin DANGLOT

For now, we discard this case #383 in order to have functional A-amplification.

Hello @andrewbwogi thank you for taking care of this. > It seems like cases to let arrays be observed must be added to AssertGeneratorHelper.isStmtToLog. Yes, I think it is the...

Hi @andrewbwogi I suggest to first merge the support of primitive arrays, and then let you continue on complex object arrays, WDYT?

Hi @Deeplus, You can have a look at this maybe. It will allow you to go through different input amplifiers and input budgetizers without necessarily need to know every piece...

Hello @firhard Thank you for the report. I would say that the problem is the value you specified to the `--pit-filter-classes-to-keep`, _i.e._ `org.joda.time.field.UnsupportedDurationField`. Here, you should specify the topest package...

Hello, Sorry for the delay. It seems that the problem comes from the fact that PIT cannot find the test classes. From your logs, we can see the following: ```txt...

Hello, > Is there any reason why the JacocoCoverageSelector could kill more mutants than the PitMutantScoreSelector? Do you mean that the amplified tests obtained with the JacocoCoverageSelector obtain a better...

The progress bar uses the number of test methods to be amplified. So **DSpot** amplifies 89% of 200 test methods. > Would be great to have progress since right now...

Hello, It seems great! Actually, it would start to resolve an important problem in DSpot: the number of amplified test by input amplification. For now, most of input amplification are...

Hello, DSpot runs only (for now) on maven project. Does `scheduling` is a maven project? According to your relative path to the source project: `src=../scheduling/scheduler/scheduler-api/src/main` You are targeting a multi-module...