pietrobraione / tardis Goto Github PK

Right now all the output emitted by TARDIS is done by plain old System.out.println. We should use a logging framework instead.

Filtering of duplicates during seeding does not work in all cases. For example, it does not eliminate tests that have exactly the same path condition.

TARDIS systematically hangs when seeding is active and the target is a single method. After seeding apparently the EvoSuite performer does not process any job, but the termination manager does not detect it as terminated, so it is stuck in a busy wait.

If seeding generates test cases number 0, 1, ... n, subsequent tests are generated starting from 1, and overwrite the tests generated by seeding. Numeration must be fixed.

The situation where a test does not hit a target method may arise in some corner cases, e.g. with degenerate seed tests. These situations must be detected and correctly handled.

Right now exception are badly managed. They are typically caught close to their source, reported to the console and not propagated. We should distinguish between the exception that generate warnings, exception that somehow affect the workflow, and exception that abort TARDIS (if any), and properly handle them. This is not so simple given the multithreaded architecture of TARDIS, so some study on how exception propagation mixes with the executor framework is required before attempting such an endeavour.

Build getting failed while building sushi-lib with gradle build -x test.