Just to let you people know,
The idea I have, is to use WicketTester against a real EJB deployment. The benefits would be: - a lot faster than Selenium tests - using WicketTester API - testing EJB calls as they are really used from wicket actions (especially with regards to lazy loading as I am not using Open-Session-In-View) - testing against deployed EAR as produced by build script, therefore testing build and EAR deploybility
This works rather nicely, but you need Arquillian so you can really run the Test within the server deployment. (No way with remote lookups or CDI emulations...) But then WicketTester is a great tool to automate use case testing. Cheers, Tom. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
