Make constrained refinement testable

[GoogleCodeExporter]

Refactor Bisimulation to allow some modular testing of the refinement process. 
Specifically, do this for refinement based on constrained counter-example 
paths. Potentially also refactor non-constrained parts of Bisimulation to allow 
more fine-grained testing of those as well.

Original issue reported on code.google.com by tonyohm...@gmail.com on 6 Aug 2013 at 11:00

[GoogleCodeExporter]

The work done by getSplits(...) is currently only split into constrained and 
unconstrained versions, and all functions are private.  We'll need to make the 
functions that getSplits(...) calls public.  Currently, this is only 
getSplitsConstrained(...) and getSplitsUnconstrained(...), but we should also 
refactor the work done by these two into pieces.

Possibly we could have each of the aforementioned functions be split into two: 
one to find which partition to split on and one to find actual divisions of 
events within that partition (actual splits) which are legal and useful.

Original comment by tonyohm...@gmail.com on 8 Aug 2013 at 6:43

[GoogleCodeExporter]

While refactoring Bisimulation, it would also be helpful to make the class 
stateful.  Currently all methods are static.  We haven't yet decided how 
drastic changes toward this end should be.

Original comment by tonyohm...@gmail.com on 12 Aug 2013 at 5:54

[GoogleCodeExporter]

We now have sufficient tests without having had to refactor.

Original comment by tonyohm...@gmail.com on 24 Oct 2013 at 9:29

• Changed state: WontFix