From: Marc G. <mgu...@ya...> - 2005-02-03 08:50:54
|
Personnally I mainly consider htmlunit only as a browser (the one I use inside webtest) and therefore I think that assertXXX methods have nothing to do in the main "browser" classes. Nevertheless, for your 2 examples: - instead of HtmlPage.clickLinkWithText(String), we could imagine a HtmlPage.getAnchorWithText(String).click() (there is already getAnchorByHref()) - instead of HtmlPage.assertTitleEquals(String), we could imagine a base unit test class providing utility like assertTitleEquals(String, HtmlPage). This would avoid to have the test methods leak in the "browser". Marc. Gredler, Daniel (Matrix) wrote: > Hi, > > I recently ran across jWebUnit (http://jwebunit.sourceforge.net/), which is > essentially an extension of HttpUnit, allowing unit testing using more > concise code. It includes convenience methods like clickLinkWithText(String) > and assertTitleEquals(String). What do you guys think about adding this kind > of ease-of-use methods to HtmlPage, for example? > > Regards, > > Daniel > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > HtmlUnit-develop mailing list > Htm...@li... > https://lists.sourceforge.net/lists/listinfo/htmlunit-develop > |