On May 7, 2010, at 9:58 AM, Vincent Massol wrote: > > On May 7, 2010, at 9:52 AM, Thomas Mortagne wrote: > >> On Fri, May 7, 2010 at 09:42, Sergiu Dumitriu <[email protected]> wrote: >>> On 05/07/2010 09:14 AM, Vincent Massol wrote: >>>> Hi, >>>> >>>> Right now we check pages in our functional tests (xhtml validity, no error >>>> when executing the page, no failing macro). >>>> I was wondering about the idea of having the checks done inside wiki pages >>>> so that we could provide a sanity check wiki page in the admin section for >>>> admins. >>>> Then we would use that page from our junit test and people would also be >>>> able to run it too from inside their wiki. >>>> Thus killing 2 birds with one stone >>>> I think we're lacking such kind of tools for wiki admins and it could be >>>> interesting. >>> >>> You mean some velocity/groovy script which checks things in the wiki, >>> like "does the document X exist, does the document Y have PR, does the >>> class Z exist", right? Yes, I like the idea. >> >> No I think Vincent is talking about putting our XHTML/WCAG validity >> tests inside the wiki instead of executed from junit tests during the >> buid. > > > Current list: > - XHTML validity > - no failing macro > - no velocity warning (would require the ability to capture the console logs > - we need that anyway, app logs should not go in the main xwiki logs and > should accessible from the wiki itself) > - <add ideas here>
- check for page rendering exception see below. > Note: For the "wanted links"/"broken links", it might be better to have it as > a tab in the alldocs page IMO since this is useful not only to admins but > also for users. > > Thanks > -Vincent > >> >> But those tests would be useful yes. >> >>> >>> Another idea would be to write selenium tests as HTML tables and run >>> them from the browser, this would allow to run the tests both from mvn >>> and from the running wiki. Creating a language (DSL) for writing tests that affect all pages could be done too yes but it would be hard I think (for these use cases). Having a simple TestCaseClass with one text area for wiki syntax content to execute is simple. Then have an executor that iterate over all pages and execute all the scripts in TestCaseClass objects found. -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
