Re: [xwiki-commits] r3571 - in xwiki/trunk/application-test: . src/test/it/com/xpn/xwiki/it/framework
On Jun 8, 2007, at 9:34 AM, Catalin Hritcu wrote:
Author: hritcu Date: 2007-06-08 09:34:30 +0200 (Fri, 08 Jun 2007) New Revision: 3571
Modified: xwiki/trunk/application-test/pom.xml xwiki/trunk/application-test/src/test/it/com/xpn/xwiki/it/ framework/AbstractXWikiTestCase.java xwiki/trunk/application-test/src/test/it/com/xpn/xwiki/it/ framework/AlbatrossSkinExecutor.java Log: Removed dependency on XMLUnit.
Just to explain: I've agreed with Catalin to remove it because the code we get is HTML (not XHTML) and xmlunit requires valid XML so the combo wasn't working that great. It's also simpler just to use Selenium's internal xpath feature. -Vincent
Hi, On 6/8/07, Vincent Massol <[email protected]> wrote:
On Jun 8, 2007, at 9:34 AM, Catalin Hritcu wrote:
Author: hritcu Date: 2007-06-08 09:34:30 +0200 (Fri, 08 Jun 2007) New Revision: 3571
Modified: xwiki/trunk/application-test/pom.xml xwiki/trunk/application-test/src/test/it/com/xpn/xwiki/it/ framework/AbstractXWikiTestCase.java xwiki/trunk/application-test/src/test/it/com/xpn/xwiki/it/ framework/AlbatrossSkinExecutor.java Log: Removed dependency on XMLUnit.
Just to explain: I've agreed with Catalin to remove it because the code we get is HTML (not XHTML) and xmlunit requires valid XML so the combo wasn't working that great.
To be even clearer about this: we get HTML that is not valid XML even though the original documents we feed to the browser are perfectly valid XML/XHMLT. It's just how browsers work, and Selenium can do little to compensate for this. Regards, Catalin
participants (2)
-
Catalin Hritcu -
Vincent Massol