Elizabeth Keogh wrote:
Forwarding this from the BDD group...
Hi Rob,
And I'm having some trouble getting my specs to run in Eclipse....
When I try to Run As JUnit Test, a dialog pops up that says "No
JUnit tests found."
Annoyingly, Eclipse can't find annotations if they're contained within
a jar, even if they're runtime persisted (haven't tested this; just my
perception). If you give it the source, it sorts itself out.
If you add the source jar (download from
http://jbehave.org/software/download/ ) as the source for the JBehave
library you should find that it works OK for the later versions of
Eclipse. If you're using earlier versions, try making your own
<MyApplicationScenario> which extends Scenario, and extend and
super.run() the run() method of Scenario. Put your own @Test
annotation on it. It's ugly* but it works**.
*I'm also finding that having that practice is great anyway, because
usually I'm reusing the same Steps and have some custom matchers etc.
that are easily accessible. And, JBehave2 is crazily configurable, and
there might be some stuff there that's useful at a project level...
once we get the documentation up. Adapters between you and your third
party libraries is a good practice, and we love our tests, I mean
examples, the same way we love our production code.
** This is mentioned on the jbehave.org download page, but we need to
get a FAQ or something on the website somewhere... thank you for the
nudge, Rob!
Hi Liz,
I've added http://jbehave.org/documentation/faq/ page and updated
http://jbehave.org/software/download/ page to have direct link to
sources jar.
Note that I've moved the NB to
http://jbehave.org/documentation/ide-integration/ (now that it's also in
the FAQ).
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
