No, Context (as I suggested) was executable in a steps class.
@Context(" once for each browser/os")
public void eachBrowser() {
MultiRunScenarioExecutor execr = new MultiRunScenarioExecutor();
execr.addRun(new ScenarioRun() {
// set firefox + linux
// set data prefix '01'
});
execr.addRun(new ScenarioRun() {
// set IE + windows
// set data prefix '02'
});
execr.addRun(new ScenarioRun() {
// set safari + macos
// set data prefix '03'
});
super.getContext().replaceScenarioExecutor(execr);
}
@Context(" once for each browser/os in parallel")
public void eachBrowserInParallel() {
eachBrowser();
MultiRunScenarioExecutor execr = (MultiRunScenarioExecutor)
super.getContext().getScenarioExecutor();
execr.setParallelExecution(true);
}
Regards,
- Paul
On Mar 6, 2009, at 2:08 PM, Mauro Talevi wrote:
Dan North <tasta...@...> writes:
Maybe invert it and call it Constraint.
But it's not clear to me what the use case of this Context/
Constraint is.
I mean if it's only descriptive, then Scenario should suffice.
Remember that you
can have a scenario description over as many lines as you need and
it's free
text so you can just as well add a Context: section.
If it isn't only descriptive then can you detail how you'd use it?
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
