Wow, that makes a few interesting things! Thanks! :-) Pierre
On Tue, Aug 12, 2014 at 9:47 AM, Martin Grigorov <mgrigo...@apache.org> wrote: > Hi, > > For Wicket's JS we use QUnit. > https://github.com/apache/wicket/tree/master/testing/wicket-js-tests is a > Maven module responsible to execute the unit tests. It uses > https://github.com/eirslett/frontend-maven-plugin to download Node.js and > to execute Grunt. See > http://wicketinaction.com/2014/07/build-resources-with-node.js/ for more > details. > The tests themselves are at > https://github.com/apache/wicket/tree/master/wicket-core/src/test/js. > Our CI server runs Maven with -Pjs-test. > > Additionally we have UI tests at > > https://github.com/apache/wicket/tree/master/wicket-examples/src/main/webapp/js-test > which also are QUnit based but use https://github.com/martin-g/gym.js for > the UI interactions. See > http://wicketinaction.com/2012/11/javascript-based-functional-testing/ for > more details. > These tests are executed manually by visiting > http://localhost:8080/js-test/all.html > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > > On Tue, Aug 12, 2014 at 4:57 AM, Pierre Goupil <goupilpie...@gmail.com> > wrote: > > > Good evening, > > > > Are there any good practices or known solutions in order to test the > > JavaScript of a Wicket application? > > > > For the moment, I launch my tests in the Wicket pages in Jenkins, with a > > flag telling whether to display them or not depending upon the staging > > plateform: they are hidden in production and displayed in development and > > in Jenkins. > > > > And I use QUnit, which goes pretty well with jQuery code under test, > IMHO. > > > > Do you guys have a different workflow? Maybe with phantomJS or another > > headless tool? > > > > Any ideas are most welcome. > > > > Cheers, > > > > Pierre > > > -- La vie est source de joie, la mort est source de paix, seule la transition est difficile.
