Hi Alex,
Knowing that you can write specs which can be run as JUnit tests,
can't the "continuous testing" plugin in Eclipse work with that?
Or would you like something simple like autotest in Ruby which polls
the modified files regularly and executes the tests in the console if
any file is modified? I've just seen someone creating a FilePoller in
Scala. I could certainly make a good use of it then.
Eric.
PS:
BTW, the next version of specs allows you to mix-in a JUnit trait (or
ScalaTest) to a Specification like this:
class mySpec extends Specification with JUnit { ... }
The only difference with before is that your specification has to be a
class. And in that case, if you want to execute it in the console you
need to do:
// if mySpec is a class, the "run" class can be used to execute it
java -cp ... run org.mypackage.mySpec
One more thing to note, if you're a Maven user (I don't remember how
Buildr does it), you have to be careful about the Specification class
naming because by default only **/*Test files are included. I recently
made sure that all my Specifications in the project were named xxxSpec
and xxxxUnit, and I configured Maven to execute only those.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
