Re: [Lift] Less boilerplate in your specifications / tests

2010-03-01 Thread Jeppe Nejsum Madsen
David Pollak  writes:

> Eric,
>
> You're a Lift committer.  Feel very encouraged to clean up the tests!

But if you do, please have in mind that not all the niceties of Specs
are supported very well by IDEs, which may be why some tests are as they
are :-( 

Hopefully that will change when 2.8 comes out (at least for Eclipse it
will. The current workaround for running specs is quite horrible)

/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.



Re: [Lift] Less boilerplate in your specifications / tests

2010-03-01 Thread David Pollak
Eric,

You're a Lift committer.  Feel very encouraged to clean up the tests!

Thanks,

David

On Sun, Feb 28, 2010 at 4:42 PM, etorreborre  wrote:

> Hi all Lift-developers,
>
> I have noticed a few commits recently where the declarations for
> specifications could be reduced to something simpler.
>
> For example:
>
> import org.specs._
> import org.specs.runner._
>
> class BindingsSpecTest extends Runner(BindingsSpec) with JUnit with
> Console
> object BindingsSpec extends Specification
>
> can be written as
>
> import org.specs._
>
> class BindingsSpec extends SpecificationWithJUnit
>
>  - the BindingsSpec class will run with maven, provided that you add
> the proper include directive in the pom.xml file, like this, for
> example:
>
>  
>org.apache.maven.plugins
>maven-surefire-plugin
>2.4.3
>
>  false
>  -Xmx512m
>  always
>  
>**/*Unit.java
>**/*Spec.java
>  
>  
>**/*Test.java
>  
>
>  
>
>  - It will also run in the console, like this:
>
>   scala -cp  run net.liftweb.http.BindingsSpec
>
> I hope this helps, please ping me if you have any concern with this.
>
> Eric.
>
> PS: I forgot to mention that I am guilty of the situation above
> because of how things were done in specs when I starting contributing
> the first specifications to Lift,...
>
> PPS: I've edited the User Guide to make clear what was the preferred
> way of using JUnit with specs:
>
>
> http://code.google.com/p/specs/wiki/RunningSpecs#Run_your_specification_with_JUnit4
>
> --
> 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.
>
>


-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

-- 
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.



[Lift] Less boilerplate in your specifications / tests

2010-02-28 Thread etorreborre
Hi all Lift-developers,

I have noticed a few commits recently where the declarations for
specifications could be reduced to something simpler.

For example:

import org.specs._
import org.specs.runner._

class BindingsSpecTest extends Runner(BindingsSpec) with JUnit with
Console
object BindingsSpec extends Specification

can be written as

import org.specs._

class BindingsSpec extends SpecificationWithJUnit

 - the BindingsSpec class will run with maven, provided that you add
the proper include directive in the pom.xml file, like this, for
example:

  
org.apache.maven.plugins
maven-surefire-plugin
2.4.3

  false
  -Xmx512m
  always
  
**/*Unit.java
**/*Spec.java
  
  
**/*Test.java
  

  

 - It will also run in the console, like this:

   scala -cp  run net.liftweb.http.BindingsSpec

I hope this helps, please ping me if you have any concern with this.

Eric.

PS: I forgot to mention that I am guilty of the situation above
because of how things were done in specs when I starting contributing
the first specifications to Lift,...

PPS: I've edited the User Guide to make clear what was the preferred
way of using JUnit with specs:

http://code.google.com/p/specs/wiki/RunningSpecs#Run_your_specification_with_JUnit4

-- 
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.