Sergiu Dumitriu wrote:
jvdrean (SVN) wrote:
Author: jvdrean
Date: 2008-10-10 11:53:57 +0200 (Fri, 10 Oct 2008)
New Revision: 13481
Log:
XE-319 : Write an integration tests framework for the new wysiwyg editor
Initial version, the XHTML assertions must be reviewed since some behaviors looks weird.
Should we test the internal HTML? Or the generated wiki syntax? Marius,
do all the browsers have the same markup? AFAIK, no, so this is a point
against testing HTML. Testing the wiki syntax implies testing not just
the editor, but also the html parser.
One of the things I'm working on is to make all browsers generate the
same markup, because the problem is not only that each browser generates
its own markup but also that they expect and behave right under specific
markup, while the input of the editor is just one, comes from the
rendering and is browser independent.
I don't think we should test the generated wiki syntax with Selenium.
This part is well covered in Vincent's unit tests. I think JV should
JV is working on the DSL for the functional tests. Me and Marcela are
going to write them. We might need help, depending on how long it will
take to write them (supposedly not too long).
focus on editor behavior, which sometimes requires
inspecting the
generated HTML (like in the case of "Return should generate a new
paragraph"). We need functional tests for the editor as for an
independent widget.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs