Yes!
Who will be the first to write a JUnit test case to test save and restore of
Figs?
/Linus
2009/1/16 Tom Morris <[email protected]>
> > So, the problems in the sequence diagrams was not isolated there.
> >
> > What issue or issues document these problems? Who is on top of this?
>
> 5623 - getLineWidth not visible in FigLifeLine (fix reportedly merged
> into alpha3)
> 5624 - PathConvPercent used instead of PositionPathItem in
> FigEdgeModelElement (affecting Association Class), FigMessage
> 5625 - PathConvPercent used in FigGeneralization
>
> All have been fixed in HEAD, although I've left issue 5624 open at
> lower priority while asking Dave to review the fix to
> FigEdgeModelElement.
>
> The problems reflect a weakness in the unit tests. There are no
> automated tests which make sure all Figs can be saved and restored.
> It takes manual testing to verify any changes that affect persistence
> and because it uses reflection it's not obvious what things will
> affect it.
>
> Tom
>
> ------------------------------------------------------
>
> http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1028765
>
> To unsubscribe from this discussion, e-mail: [
> [email protected]].
>
