On Wed, Feb 24, 2010 at 6:34 PM, Timothy Perrett <timo...@getintheloop.eu> wrote: > Thanks for the follow up David. Probably this highlights some issues with our > automated testing though... any ideas on how we could add something to the > build cycle to verify stuff like this? The parsers particularly probably > could do with some pretty rigours test cases as this is a classic example... > on a related note, Heiko just found a strange character encoding bug with 2.8 > and XML; having more test cases will help us keep consistency during the > porting. > > Cheers, Tim
It could be nice if it was possible to simulate browser request/response cycles. This would allow very high level tests to be made without the need of a running container/browser etc. This is no replacement for unit tests, but is more a lightweight integration test that exercises a big part of the Lift stack.... /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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.
