Feature/persistent counter examples

[alfert]

As discussed in #10 this is an implementation of persisting counter examples between test runs. The basic idea is to have a manager of counter examples called CounterStrike which stores all found counter examples as DETS on disk.

When running a property, it is checked whether counter examples exists and if yes, then only the counter examples are executed and no other properties. This helps to focus on solving the failing properties with the same counter example to ease debugging.

[evnu]

I haven't read all of the source yet, so please forgive me if this question would be answered by the source: How does persistency cope with running single properties? E.g., if I run a single property with mix test test/some_file:123, will I lose all other stored counterexamples?

[alfert]

Yes, that would be the case. You could however save the file somewhere else and reuse it later. The integration of CounterStrike into the property macro has to be done, yet. Von unterwegs gesendet

…

Am 29.08.2017 um 10:33 schrieb Magnus ***@***.***>: I haven't read all of the source yet, so please forgive me if this question would be answered by the source: How does persistency cope with running single properties? E.g., if I run a single property with mix test test/some_file:123, will I lose all other stored counterexamples? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.