i've looked into junit etc. and thought a bit about ecs case testing
you're right that testing ecs should be like testing velocity - the
major difference being that in ecs, java test classes would take the
place of velocity templates. if you think that it's worth going ahead
and developing a jUnit test for that encoding problem (i do), i'll go
ahead and talk to gier about recycling some of the velocity basic
testing code.
the one wrinkle is of course that we'd start off by testing that html
was identical rather than equivalent (i've written something down to try
and make it clear what i mean by this) but i think that this should be
fine for now.
(aside - equivalent documents
to determine whether two html documents are logically equivalent is
actually a much more difficult task than determining whether their files
are identical. determining whether two xml documents are equivalent is
non-trivial but easier. i'd say that the easiest way to determine
equivalence would be to convert html->xhtml and then compare the xml
documents. )
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
