> I'm looking at the Testify framework, and while it looks promising, it still > doesn't connect up the spring layer. > > It also puts a /foo in front of every asset and page link on my page. > Frustrating....
The "/foo" is a default context that Tapestry adds when using its testing features. It looks annoying but it is kind-of useful because it makes sure you are testing with a context value and helps avoid your features working when there is no context and then breaking when there is one (only likely to happen for low-level URL mangling features though). I have looked at connecting the Spring layer into tests and it is quite hard to do. The tapestry-spring integration doesn't provide hooks that allow it to work outside a web container - it could do with some refactoring to allow this :-) In case it helps, here's what my projects are doing: we do acceptance testing using Fitnesse with a full Spring container and the tests start just below the web UI. Then we unit test Tapestry components with Testify and integration test the whole lot with a small number of Selenium tests. We also use Selenium for any rich UIs with Ajax or Javascript. Paul --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
