another question: is there any way (or need) to stop the Jetty server?
Usually running my tests Jetty starts up in about a second or two, but
once in a while it will take 10s or more, could this have to do with a
previous instance hanging around or not been shut down properly?
On Nov 11, 12:05
On Fri, Nov 13, 2009 at 8:30 AM, Alex Black a...@alexblack.ca wrote:
another question: is there any way (or need) to stop the Jetty server?
No.
Usually running my tests Jetty starts up in about a second or two, but
once in a while it will take 10s or more, could this have to do with a
What are you unhappy about? Those tests look pretty simple and slick
to me!
It looks like the JettyTestServer is a singleton inside the test suite
- what happens if you have another test suite? I think you'd then hit
the same problem that I did, when the second test suite tries to fire
up Jetty
On Wed, Nov 11, 2009 at 7:09 AM, Alex Black a...@alexblack.ca wrote:
What are you unhappy about? Those tests look pretty simple and slick
to me!
Yeah, but with this change: http://reviewboard.liftweb.net/r/95/
You'll get:
Login in {
for{
login - post(/api/login, token -
Looks nice.
Singleton - ah, yes, that sounds like it will work well, good call.
On Wed, Nov 11, 2009 at 12:05 PM, David Pollak
feeder.of.the.be...@gmail.com wrote:
On Wed, Nov 11, 2009 at 7:09 AM, Alex Black a...@alexblack.ca wrote:
What are you unhappy about? Those tests look pretty
Cool, I am trying that out. It seems to work well, but jetty takes abouts 2s
to fire up, any tips on reducing that?
--
From: Jonathan Ferguson j...@spiralarm.com
Sent: Monday, November 09, 2009 10:50 PM
To: liftweb@googlegroups.com
Subject: [Lift] Re: Unit testing
My first unit test worked fine, but my second one dies:
ERROR - Failed to Boot
java.lang.IllegalStateException: Cannot modify after boot.
at net.liftweb.http.RulesSeq$class.safe_$qmark(LiftRules.scala:885)
at net.liftweb.http.RulesSeq$class.prepend(LiftRules.scala:892)
at
I've just committed simple API test code up to the ESME project. The key
pieces are at:
http://svn.apache.org/viewvc/incubator/esme/trunk/server/src/test/scala/org/apache/esme/api/ApiTest.scala?revision=834618view=markup
We fire up Jetty populate a temp database and then run a batch of tests.
Seems to work well for us.
Jono
2009/11/10 Alex Black a...@alexblack.ca
Can anyone suggest some good examples or strategies to use to test a
webservice written with Lift?
I've started down the path of firing up Jetty
