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
