7 May
2010
7 May
'10
9:14 a.m.
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.
WDYT?
Thanks
-Vincent
7 May
7 May
9:42 a.m.
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.
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.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
9:52 a.m.
On Fri, May 7, 2010 at 09:42, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
On 05/07/2010 09:14 AM, Vincent Massol wrote:
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.
But those tests would be useful yes.
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.
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.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
9:58 a.m.
On May 7, 2010, at 9:52 AM, Thomas Mortagne wrote:
On Fri, May 7, 2010 at 09:42, Sergiu Dumitriu
<sergiu(a)xwiki.com> wrote:
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>
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
On 05/07/2010 09:14 AM, Vincent Massol wrote:
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. 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.
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.
10:12 a.m.
On May 7, 2010, at 9:58 AM, Vincent Massol wrote:
On May 7, 2010, at 9:52 AM, Thomas Mortagne wrote:
- check for page rendering exception
see below.
On Fri, May 7, 2010 at 09:42, Sergiu Dumitriu
<sergiu(a)xwiki.com> wrote:
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> On 05/07/2010 09:14 AM, Vincent Massol wrote:
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. 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. 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
2:39 p.m.
I'm +100 on this one, and I would like to see this also available in the
"information" tab as well as being a "post-edit" proposal to the
user.
Like adding at the top of the page.
"Thank you for your contribution, you can check the validity of your
page using this link"
or something like that
We also need to review the "programming" right so that we also get some
warnings / errors if user try to modify a page that would be affected by
the change (like scripts needed programming right would now fail).
It's a bit off-topic but goes in the "verification" section.
Ludovic
Le 07/05/10 09:58, Vincent Massol a écrit :
On May 7, 2010, at 9:52 AM, Thomas Mortagne wrote:
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
On Fri, May 7, 2010 at 09:42, Sergiu
Dumitriu<sergiu(a)xwiki.com> wrote:
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>
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
On 05/07/2010 09:14 AM, Vincent Massol wrote:
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. 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. 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.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
10:56 a.m.
Sergiu Dumitriu wrote:
On 05/07/2010 09:14 AM, Vincent Massol wrote:
I wonder if we could have tests written in groovy which are parsed and serialized in the
wiki and output
through a page in the browser and deserialized and instantiated in selenium.
It's a long shot but it would be very cool if applications could carry their tests
around with them.
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.
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.
5246
days inactive
5246
days old
6 comments
5 participants
participants (5)
-
Caleb James DeLisle -
Ludovic Dubost -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol