I use QUnit as testing library. Node.js is required only to automate the run of the tests (in headless mode) in PhantomJS (WebKit).
At the moment I run the tests by just loading http://localhost:8080/js-test/all.html in any browser. Try it! You will like it! I'll merge the branch soon. On Mon, Jun 17, 2013 at 8:13 PM, Cedric Gatay <gata...@gmail.com> wrote: > Testing JS is a good thing to me, is there any other javascript testing > framework without such prerequisite (Node.js) ? At SRMvision, we use > Jasmine which does not require any other setup. > > Anyway, I think it should be part of the Maven build process if we want > them to be useful. > > Regards, > > __ > Cedric Gatay (@Cedric_Gatay <http://twitter.com/Cedric_Gatay>) > http://code-troopers.com | http://www.bloggure.info | > http://cedric.gatay.fr > > > On Mon, Jun 17, 2013 at 4:20 PM, Martijn Dashorst < > martijn.dasho...@gmail.com> wrote: > > > No problem... the more tests the merrier > > > > Martijn > > > > On Mon, Jun 17, 2013 at 3:05 PM, Martin Grigorov <mgrigo...@apache.org> > > wrote: > > > Hi, > > > > > > I just pushed branch "wicket-examples-gym-tests". > > > It contains some tests based on the idea described at > > > http://wicketinaction.com/2012/11/javascript-based-functional-testing/ > > > > > > To run the tests one has to start the examples and load > > > http://localhost:8080/js-test/all.html > > > > > > Is there anyone against these tests ? > > > I'd like to add some coverage to Wicket Examples and to practice my JS > > > coding skills. > > > > > > At the moment both the old JS tests (wicket-core/src/test/js) and these > > > ones should be executed manually. I can integrate them in Maven but > them > > > all developers and CI machines should have Node.js > > > Do we want the tests in the build or should I leave them as now ? > > > > > > > > -- > > Become a Wicket expert, learn from the best: http://wicketinaction.com > > >
