pietrobraione / sushi-lib Goto Github PK

Currently the path condition evaluator is limited to evaluating symbols in the initial execution state. However function symbols standing for method invocations can be generated in intermediate states, so they should be evaluated there. The only way I can think this can be implemented is to rewrite the path condition evaluator so its performs concrete execution of the test with JBSE.

The wrapper classes emitted by the formatters give name to the test0 method's variables from the variable names of the method under test. If no debug information is present in the class such names are absent, and the formatters use the default names given by JBSE to the variables, that are not well-formed Java names.

The wrapper class emitted by a formatter is declared in the top-level package. This does not allow the formatter to access to package-level members of the class. The wrapper should be modified to emit the wrapper class in the same package as the target class.

If a test diverges (i.e., does not terminate), the coverage calculator hangs. This means that diverging tests must be detected by hand and excluded before running the coverage calculator, potentially missing some target that these tests may cover. Introduce some form of timeout for test execution so the coverage calculator will abandon the execution of the test and progress.