I'm surprised at the lack of information about how to get the page tester wired up correctly in tapestry 5.1 to use spring beans. It looks like the API for the the SpringModuleDef changed between 5.0 and 5.1 for connecting the page tester to the spring context.
Testing a Tapestry application outside of a container using JUnit (or TestNG) is prerequisite for new development. Simply saying "use Selenium" is not acceptable. I've worked on teams that have used Tap 3, 4.0, and 4.1, and have started to build new apps using 5.1, but this is a show-stopper for me. I'm disappointed because I think Tapestry is the best solution out there right now. -- View this message in context: http://old.nabble.com/Unit-testing-with-tapestry-5.1-and-spring-tp28141440p28141440.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
