The bdd by example article is using jbehave 2, that will require quite a
bit adapting to work with a current version.
There are a few articles links at http://jbehave.org/users-experiences.html.
On 06.09.2012 23:26, Mani Sarkar wrote:
HI,
Can anyone suggest useful Jbehave tutorials that I cou
Yes I noticed that, which is why I joined the group to find out about the
intricacies of jbehave! I fixed the issues it was okay, except for pending
issue.
Thanks for the reference.
On 6 Sep 2012 23:56, "Alexander Lehmann" wrote:
> The bdd by example article is using jbehave 2, that will require
What is your pending issue?
On 07/09/2012 17:20, Mani Sarkar wrote:
Yes I noticed that, which is why I joined the group to find out about
the intricacies of jbehave! I fixed the issues it was okay, except for
pending issue.
Thanks for the reference.
On 6 Sep 2012 23:56, "Alexander Lehmann"
I get the below, and can't tell why its throwing this error - I checked the
types of the two variables and they are the same yet all the assertThat()
calls return similar errors as below.
java.lang.AssertionError:
Expected: <[E1, A1, D2, G3, B4, B4, B4, e7, e5]>
got: <[E1, A1, D2, G3, B4, B4,
Mani,
this has nothing to do with JBehave. You doing an assertion between to
variable, using Assert.assertThat() which in turn uses Hamcrest's Matcher.
Try experimenting with matchers in separate unit tests using the
variables that you've specified.
Cheers
On 09/09/2012 22:55, Mani Sarkar
