When description is stored in a separate file and comparation is active, when
the final activity of a trace compares equal to a previous one, its description
is discarded.
This leads to the generation of assertions in the JUnit test cases that will
never be true, because referring to an equivalent, yet not equal, state
description.
Original issue reported on code.google.com by nofatclips on 20 Mar 2012 at 11:33
Original issue reported on code.google.com by
nofatclips
on 20 Mar 2012 at 11:33