To be honest I really really feel that's what Jbehave are bringing to
the scene :)
And I haven't found something that's as simple and clean as Jbehave, all
the other BDD I've seen involves a lot of "uglyness" to archive the
same, at least in java anyway. I like my code to be clean and short and
in the same time easy understandable.
Dan North wrote:
I'm loving the word "testalicious" :)
2008/11/16 Nino Saturnino Martinez Vazquez Wael
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
Looks fine..
I did something similar on my blog, although a bit more general:
http://ninomartinez.wordpress.com/2008/11/03/testalicious_testing/
Alexandre Martins wrote:
I've just finished a post about using JBehave and Selenium
together, designing the steps based on the Page Objects pattern.
http://blog.m.artins.net/acceptance-tests-with-jbehave-selenium-page-objects/
Any feedback would be welcome.
Cheers.
Alex.
On Fri, Oct 31, 2008 at 6:11 AM, Nino Saturnino Martinez
Vazquez Wael <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>> wrote:
Okay great, do you have some code sniplets on usage of it?
Btw i'll post a blog entry on it when I've setup the basic
parts:)
Paul Hammant wrote:
So has anyone done that?
Yes I have.
JBehave2.1 is better for Selenium than 2.0.
The the work in a setUp method in the Scenario :
public class DoSomeThing extends JUnitScenario {
Selenium selenium;
public void setUp() {
selenium = // whatever
super.addSteps(new SomeSteps(selenium, getConfig()));
}
// close the selenium in a tearDown()
}
See also the new performing(..) method on StepsMonitor.
The
config can accept a useMonitor(..) method to use a new
StepsMonitor impl that routes through to
Selenium.setContext(..) for extra information in the
browser
as tests are running.
- Paul
If not im thinking of doing it. It turned out that the
direct wicket
integration had some problems...
Currently Im not sure how I do some things before and
after a scenario
are run? I tried to override runAfterScenario &
runBeforeScenario but
both seemed to run before my scenario or anyway be
fore my
steps were
called, so Im thinking that I misunderstood something?
// @Override
// public List<Step> runAfterScenario() {
// selenium.stop();
// try {
// Start.stop();
// } catch (Exception e) {
// // TODO Auto-generated catch block
// e.printStackTrace();
// }
//
// return super.runAfterScenario();
// }
//
// @Override
// public List<Step> runBeforeScenario() {
// Start.start();
// try {
// selenium =
createSeleniumClient("http://localhost:8080/";);
// selenium.start();
// } catch (Exception e) {
// // TODO Auto-generated catch block
// e.printStackTrace();
// }
//
// return super.runBeforeScenario();
// }
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
_
Alexandre Martins
http://blog.m.artins.net
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
