Hello good Wicket People, I now have a cool Wicket+CDI/Weld+EJB EAR running in JBoss AS7. Before it progresses further, I should start adding some automated integration tests, I think ;-)
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 Does that sound like a good or like a stupid idea to you ? Do you have other/better ideas other than solo plain EJB unit tests (do not test usage from Wicket), solo WicketTester (does not test calls to EJB layer) and Selenium (too slow and complicated to use for all tests) I'm a bit lost at the moment, using WicketTester from JUnit test case is easy, but when I try to lookup the BeanManager to setup CDI, it does not work, as the "remote" WicketTester is not allowed to remotely lookuop "java:comp/env/BeanManager"... Maybe I need to start WicketTester within the Arquillian-started (or Cargo-started) JBoss... Somebody having a remotely similar setup working ? (There are several examples for Spring, but not easily adapted to an EJB layer running in an un-embedded server...) Any input appreciated... Thanks, Cheers, Tom. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
