iirc : * jetty was more for "integration testing" than unit/code test, with jetty + webunit I could (re)play from client to server to client and test a workflow between several page * winstone + winstone maven plugin was to generate standalone jar, user could download sample and with "java -jar xxxx-standalone.jar" * test of lift-archetypes is more about testing that archetype generate "correct" project
/davidB On Fri, Oct 31, 2008 at 12:27 AM, David Pollak <[EMAIL PROTECTED]> wrote: > There are a couple of testing things that need to get woven together. > > Specs is a great way to write code-level tests. > > Lift's testkit is pretty good for writing REST tests and okay for writing > JSON tests. > > There's no good way to write automated tests for the Lift HTML layer. :-( > > On 10/30/08, Erick Fleming <[EMAIL PROTECTED]> wrote: >> >> I'm exploring testing, in Lift, and would like create some >> documentation on the topic, but I'm not sure what direction to go in. >> >> I gather from tests in the lift-example that Specs with JUnit 4 is the >> current perferred frameworks. But, the lift archetypes has a >> different approach. >> >> I'm also confused with the winstone dependency in the example. >> Doesn't jetty serve this purpose? > > I've removed Winstone from the file. I don't know how it got in there. :-( > >> >> So, what are your practices to for testing Lift applications. >> > > > > -- > Lift, the simply functional web framework http://liftweb.net > Collaborative Task Management http://much4.us > Follow me: http://twitter.com/dpp > Git some: http://github.com/dpp > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
