gmane.comp.java.jbehave.user

Re: Re: Handling failure in Parameterized scenarios

Paul Mander — 2013-05-24T11:12:40

Thanks Christian,

It would appear that the best solution for this particular application is
to delete the cookies on the first step just before the get.

Regards,

Paul


On 24 May 2013 08:27, Karlsson Christian <Christian.Karlsson-VP0q8vyylVw< at >public.gmane.org> wrote:

SV: Re: Handling failure in Parameterized scenarios

Karlsson Christian — 2013-05-24T07:27:10

Hi Paul
To achieve 'b' in your question I remove session cookies at the end of a scenario. Could that be a solution for you perhaps?

    < at >AfterScenario
    public void destroy() {
        webDriverProvider.get().manage().deleteAllCookies();
    }

Regards,
Christian


Christian Karlsson
CAG Contactor AB
Adress: Jan Stenbecks Torg 17, SE-164 40 Kista
Mobil: +46 (0)706694527
Mail: christian.karlsson <at> cag.se
www.cag.se<https://wmail.cag.se/owa/redir.aspx?C=G2EjVQkj7kGZyieqy24uGB6NV2uAkM9Iy3xqV4cZFUaEVGXCGlWIq_V5O25t1jIUtjHgAaGFl0U.&URL=http%3a%2f%2fwww.cag.se%2f>

Från: Paul Mander [mailto:paul.s.mander-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org]
Skickat: den 23 maj 2013 17:14
Till: user
Ämne: [jbehave-user] Re: Handling failure in Parameterized scenarios

I have a sort of solution.

I can add the following to a step class

        < at >AfterScenario(uponType=ScenarioType.EXAMPLE, uponOutcome=Outcome.FAILURE)
                      public void end() throws Exception {

Re: Re: Handling failure in Parameterized scenarios

Mauro Talevi — 2013-05-23T22:06:45

Yes, that'll work.  Were you looking for an alternative solution?

On 23/05/2013 17:14, Paul Mander wrote:

Re: get Story name inside < at >BeforeStory

Mauro Talevi — 2013-05-23T22:01:54

You can use meta parameters.

http://jbehave.org/reference/stable/meta-parametrisation.html

https://github.com/jbehave/jbehave-core/blob/master/examples/trader/src/main/java/org/jbehave/examples/trader/steps/BeforeAfterSteps.java

On 23/05/2013 16:54, Rafael Farias Silva wrote:

Re: Handling failure in Parameterized scenarios

Paul Mander — 2013-05-23T15:14:22

I have a sort of solution.

I can add the following to a step class

        < at >AfterScenario(uponType=ScenarioType.EXAMPLE,
uponOutcome=Outcome.FAILURE)
 public void end() throws Exception {
pages.loginPage().end();
}

        < at >BeforeScenario(uponType=ScenarioType.EXAMPLE)
public void start() throws Exception {
pages.loginPage().start();
 }

and then this to the page object:

        public void start() throws Exception {
 if (init) {
((RemoteWebDriverProvider) getDriverProvider()).initialize();
init = false;
 }
}

private boolean init = false;

public void end() {
((RemoteWebDriverProvider) getDriverProvider()).end();
init = true;
 }

Not very elegant but it will end the session on an example failure and
start the next one if it was ended. Not going to work for a multi-threaded
scenario though.


On 23 May 2013 14:10, Paul Mander <paul.s.mander-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

get Story name inside < at >BeforeStory

Rafael Farias Silva — 2013-05-23T14:54:33

Hello ppl,

I would like to get the Story name in a method annotated with < at >BeforeStory,
is there a way to do this?

I need this for debugging purposes, cause i'm running a bunch of stories
with runStoriesAsPaths and with multiple threads, and I'm trying to log
wich thread is running wich story.


Could someone help me? Did'nt found any question like that on google /
stackoverflow, so i'm asking here.

Thanks in advance.

Handling failure in Parameterized scenarios

Paul Mander — 2013-05-23T13:10:38

I'm using jbehave and selenium to perform regression tests on an
application as part of my CI process. I want to expand the coverage of
these tests which means running the same scenarios hundreds of time with
different data.

I am using Parameterized scenarios such as

When <user> logs on with password <pass>
Then landing page is shown
When user searches for customer <customer>
Then the customer name "<name>" is shown
When user logs off
The logon page is shown

Examples:
|user|pass|customer|name|
|test1|test1|001|Fred Bloggs|
|test1|test1|001|George Bloggs|
|test1|test1|001|Susan Bloggs|
|test2|test2|001|Fred Bloggs|
|test2|test2|001|George Bloggs|
|test2|test2|001|Susan Bloggs|

etc

I know how to configure the tests so that that continue with other stories
and scenarios if a failure happens but I need also to

a) run the example line in the example if one fails
b) start a new browser session for each example

I need 'b' because the failure would not log off the app...

Thanks

Re: Preselect testcases based on test plant capabilities

Mauro Talevi — 2013-05-18T17:33:34

Hi,

first of all, what do you mean by "testcases", is it scenarios, stories 
or groups of stories?

Secondly, what do you mean by "have nodeX" or "have nodeY"?

There are different ways to include or exclude from execution. It'd be 
best if you could provide us with a simplified sample project to better 
understand your use case.

Cheers

On 10/05/2013 14:23, Mikael Petterson wrote:

RE: Re: Repeating scenarios

Jorge Pombar — 2013-05-15T18:49:24

My apologies to pick up this old thread. This is a features that we are really interested on.

My question is for Julian, how do you "pick up randomly the stories".

Once you have the stories, how do you tell JBehave to run them again? (we only feed the stories once at the beginning of executing and haven't found a way to refeeding them to JBehave)

How to do extract the errors from the log? Do you parse the log file? Or do you access the a log object, if so how you do that?

I'll update the issue you mention below Mauro once we get some focus with our requirements

Thanks,
Enrique

From: Mauro Talevi [mailto:mauro.talevi-hQ+s5KbX5YmGglJvpFV4uA< at >public.gmane.org]
Sent: Sunday, December 23, 2012 7:05 AM
To: user-b1QraVsTlj/IJWOP8RzEEmD2FQJk+8+b< at >public.gmane.org
Subject: Re: [jbehave-user] Re: Repeating scenarios

Hi All,

just chiming in for some thoughts on this.

While I'm a firm believer in the KISS principle, and in your specific case the step implementation strategy may be the simplest solution, I do thin

Re: Jenkins and xUnit publishing error

Mauro Talevi — 2013-05-14T14:36:22

Can you provide more info on your setup?  Which versions are you using?

Can you reproduce your behaviour in a sample shareable project?

On 14 May 2013, at 13:24, makuv <turbobanan-h7QdYz1kt/Q< at >public.gmane.org> wrote:


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Jenkins and xUnit publishing error

makuv — 2013-05-14T11:24:38

Hi All,
we introduced in our company jbehave/jbehave-web based tests. Everything 
works almost perfectly, but now we are struggling with Jenkins 
configuration.
Publish xUnit test result report is configured as follow:
JBehave Pattern **/jbehave/*.xml
Checkded options: 'Delete temprorary JUnit files' and 'Stop and set the 
build to 'failed' status if there are errors when processing a result file'.
Unfortunately during builds we encounter:
...
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JBehave-3.x
ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due 
to exception
java.lang.NullPointerException
at 
com.thalesgroup.dtkit.metrics.hudson.api.type.MetricsType.isSkipNoTestFiles(MetricsType.java:80)
at 
org.jenkinsci.plugins.xunit.XUnitPublisher.getXUnitToolInfoObject(XUnitPublisher.java:191)
at 
org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:169)
at 
org.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:116)
...

Did an

Re: How to start... Netbeans, UIspec4j, etc...

Mauro Talevi — 2013-05-13T08:06:27

Hi,

JBehave IDE basic integration relies only on JUnit support.   It does 
not require Eclipse or other IDE.

There may be some classloading issues.  Have a look at FAQ " IDE can't 
seem to recognise the JUnitStory/Stories  as a JUnit test":

http://jbehave.org/reference/stable/faq.html

The IDE plugins allow you to navigate more easily between textual steps 
and Java methods but it's not mandatory.

I'm not sure if there is a Netbeans plugin, but if you find one do let 
us know and give us feedback on it.

Cheers

On 12/05/2013 19:05, András Csányi wrote:

SV: How to start... Netbeans, UIspec4j, etc...

Karlsson Christian — 2013-05-13T07:58:26

Hello

Could you possibly have 2 different versions of jUnit configured in your IDEs?

Regards,
Christian


Christian Karlsson
CAG Contactor AB
Adress: Jan Stenbecks Torg 17, SE-164 40 Kista
Mobil: +46 (0)706694527
Mail: christian.karlsson <at> cag.se
www.cag.se

-----Ursprungligt meddelande-----
Från: sayusi.ando< at >gmail.com [mailto:sayusi.ando< at >gmail.com] För András Csányi
Skickat: den 12 maj 2013 20:05
Till: user< at >jbehave.codehaus.org
Ämne: [jbehave-user] How to start... Netbeans, UIspec4j, etc...

Hi All,

I would like get some help regarding how to start to test with jBehave. I don't have any issues with BDD methodology because I've been a test engineer for many years and I have been working with BDD under .Net but I use java in my freetime and my hobby project requires testing.

So, I created a new project and I created the story file, and the step file (it contains the steps) and the embedder file which extends the JUnitStory class. According to the documentation I should run

How to start... Netbeans, UIspec4j, etc...

András Csányi — 2013-05-12T18:05:06

Hi All,

I would like get some help regarding how to start to test with
jBehave. I don't have any issues with BDD methodology because I've
been a test engineer for many years and I have been working with BDD
under .Net but I use java in my freetime and my hobby project requires
testing.

So, I created a new project and I created the story file, and the step
file (it contains the steps) and the embedder file which extends the
JUnitStory class. According to the documentation I should run this
file as it would be a jUnit file. When I run it ( right click on the
file and "Test file" menu) it says "No tests executed". However, I do
the same in Eclipse than the tests are run and I can see the results.

The jbehave, jbehave-core are added as dependency to maven and the IDE
can see the packages.

What should I do to Netbeans to have jbehave working? I really don't
want to use Eclipse because I have very deep feeling to it. :)

On the other hand, Is there any plugin for Netbeans?

The next question is about UISpec4j

Re: Preselect testcases based on test plant capabilities

Cristiano Gavião — 2013-05-10T13:15:13

Hello Mikael,

JBehave is a tool for handle the execution of BDD like textual stories
where each step line should be mapped to step methods that is contained in
any kind of java pojo class.[1]

If your testcases are java classes and its methods could be annotated with
JBehave annotations so certainly you could use JBehave with them in your
context. But probably will be best you call the testcases methods from
specific Step classes created to support your stories.

For example, you could write a story like that:

"Given that nodeX is online // in this step you must ensure that nodeX is
online. if it is not your test could fail immediately.
And noteY is offline
When customer makes a call
Then control system must wake up the nodeZ
And complete the call"

In the Step Class that you will create to map this story to java you can
reuse and call the methods of your testcases to do what you needed and
assert what you expected to get.

hope I could help,

regards,

Cristiano

[1] - http://jbehave.org/reference/stable/

Preselect testcases based on test plant capabilities

Mikael Petterson — 2013-05-10T12:23:12

Hi,

I have looked at this framework and it looks promising. Also I want to take the opportunity to ask some questions to people that knows more about it than me :)

We have a number of testcases that we use to test nodes in a telco network. Some testcases requires that we have specific nodes ( like a specific switch or server ) and if we don't have these then it is no use to run the testcases.

Let's take an example:
To run a suite of testcases  we need to have nodeX and nodeY in our test plant. So we need to verify if we have nodeX and nodeY.
If we have node X and Y run the a suite of testcases ( TestNG). Is this possible to do in Jbehave? How would this look like in a Jbehave context?

Taking it one step further would it be possible to select the testcases automatically when you know that you have nodeX and nodeY in the testplant?

Br,

//mikael

Re: Need help in evaluating BDD tools

Mauro Talevi — 2013-05-01T23:01:56

No such statistics are available to us.

On 01/05/2013 23:55, Senthil Kumar T wrote:

Need help in evaluating BDD tools

Senthil Kumar T — 2013-05-01T22:55:33

Hi,

We are about to submit our report of  BDD tools evaluation. We have couple
of questions

1. Download statistics. Want to have the download statistics. Can you
please share maven central download statistics for last 1 year or so. It
seems only the project owners can see the statistics from maven central.
(
http://stackoverflow.com/questions/8874670/maven-detailed-download-statistics-for-artifacts-of-public-repositories-like
)

2. Forum statistics. Last 1 year no. of posts, no. of users etc.

Note: Currently we prefer cucumber-jvm and already started using it on our
projects. The reason we felt is Cucumber-JVM seems simple, more active
development/discussion happening, people migrating from jbehave to
cucumber-jvm, and better github stats like stargazers, and forks.

We also observed the most compelling features from jbehave are parallel
execution and richer life-cycle events. Both can help really well for
selenium tests.

Please also share if any other differentiating features if you believe.

Thanks & R

Re: Normal build problems with jbehave-core 3.8?

Cristiano Gavião — 2013-04-24T17:49:18

Hello,
About the jenkins-ci:annotation-indexer:1.4. problem. it was because the
duplication of <id>atlassian</id> inside the settings.xml.
It seems that maven ignores have ignored the second repository.
I've changed it and send a pull request.


2013/4/24 Kendall Shaw <queshaw-65eDfwRo+1xeoWH0uzbU5w< at >public.gmane.org>

Re: Normal build problems with jbehave-core 3.8?

Mauro Talevi — 2013-04-24T17:36:39

Hi,

if you can provide a patch with the fixes you've had to implement, along 
with the output of your mvn -v, we'll have a look.

Cheers

On 24/04/2013 19:05, Kendall Shaw wrote:


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Normal build problems with jbehave-core 3.8?

Kendall Shaw — 2013-04-24T17:05:23

For reasons beyond my control, I have to develop mostly on windows xp. I 
found these problems building jbehave-core:

org.jbehave.core.embedder.ConcrrencyBehavior.shouldAllowStoriesToBeCancelled 
fails, maybe because < at >Test(expected=RunningEmbeddablesFailed.class) 
isn't honored? I removed the expected parameter and changed the timeout 
to 30 seconds to bypass the problem.

org.jbehave.core.steps.StepsBehavior.shouldProvideStepsToBePerformedBeforeAndAfterScenariosWithFailureOccuring 
fails

org.jbehave.core.steps.StepsBehavior.shouldProvideStepsToBeNotPerformedAfterScenariosUponOutcome 
fails

I haven't taken the time to figure out what the code does yet. I 
commented out the tests to bypass the problem.

Maven doesn't find jenkins-ci:annotation-indexer:1.4. I added a 
repository that has it to settings.xml.

On linux, I think it was, it only have the last problem with the missing 
dependency. So, do you know if this is expected? Should I worry?

Kendall