PiRSquared17 / easyb

Automatically exported from code.google.com/p/easyb
0 stars 0 forks source link

Run stories via JUnit #24

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Create a junit runner that executes stories-- that way users can leverage
existing infrastructure for running stories and reporting on them. 

Original issue reported on code.google.com by ajglo...@gmail.com on 23 Feb 2008 at 9:50

GoogleCodeExporter commented 9 years ago
Please include a TestNG runner also, for the same reasons. 

Original comment by aalmi...@gmail.com on 11 Mar 2008 at 10:21

GoogleCodeExporter commented 9 years ago

Original comment by ajglo...@gmail.com on 11 Sep 2008 at 12:07

GoogleCodeExporter commented 9 years ago

Original comment by ajglo...@gmail.com on 8 Sep 2009 at 1:18

GoogleCodeExporter commented 9 years ago
I think for JUnit, this would be best done using a JUnit Adaptor - one that 
lets you specify which stories or a 
classpath that will be searched for stories/specifications rather than a JUnit 
runner, which really needs to be 
annotated onto a class and is designed to run normal java tests differently.

Original comment by richard....@gmail.com on 16 Apr 2010 at 2:23

GoogleCodeExporter commented 9 years ago
Andrew has pointed out that there already is JUnit integration for easyb - 
http://code.google.com/p/easyb-
junit/

Original comment by richard....@gmail.com on 19 Apr 2010 at 6:59

GoogleCodeExporter commented 9 years ago
I will contact easyb-junit team and suggest we integrate this into core. Reach 
out to guy on mailing list to see where he is at w/integration. 

Original comment by ajglo...@gmail.com on 19 Dec 2010 at 4:22

GoogleCodeExporter commented 9 years ago
The easyb-junit runner is an approach that may suite some people however it 
breaks the nice inline easyb description. Id suggest one would want to see 
integrated junit that can already be achieved using the junit run command

TestResult r;
given "description", {
  test = new JunitTestClass("testMethodToRun")
} when "",{
  r = test.run()
} 
then "", {
  assert( true == r.wasSuccessful())
  <assert additional results>
} 

small aside, the junit test case needs a constructor that calls super on the 
method name passed

Original comment by rdonovan...@gmail.com on 9 Dec 2011 at 5:35