Hi, Having taken the first baby steps and gotten a Lift app running, it's time to bring back some of the old engineering practices to make sure things keep running when new features are added at a rapid pace :-)
I'm interested in how people are testing their Lift apps, both at the unit test level (ie. specs/scalatest with no container) and at the integration test level (running in servlet container). Also, how are you doing TDD with Lift (if at all). Specifically, I've run into the following issues: 1) Testing model classes. Many require access to S (ie to read resources) or other static Lift constructs. How can you mock these? 2) Testing snippets. Same issue with S, but more related to the actual request, eg. S.param For in-container testing it seems the practice of generating unique names for form fields, makes it difficult to use tools like Selenium to do browser based testing? How do you handle this? Any input is appreciated /Jeppe --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
