Hi Brian,
it does depend on what your aim is, i.e. just verify behaviour for
multiple browsers or run them in parallel to optimise time.
The simplest approach is to set up different run contexts for each
browser (e.g. different Maven invocations with a browser property, or
different embeddables classes - one for each browser). They can be run
in CI as different jobs and you have the advantage of spotting right
away which browser failed and where.
Else, if you need to parallelise or don't want to setup different run
environments for each browser, your best best is to use SauceLabs.
Cheers
On 10/02/2012 15:56, Brian Repko wrote:
Folks:
Any best practices for running stories in multiple browsers? - say
Firefox / IE / Chrome?
I could invoke the maven plugin 3 times. I could setup a Runner with
three @Test methods - one for each browser.
But those are serially processed (which could be ok). If I can get
the tests to run multi-threaded, then I should be able
to run different browsers in parallel too.
Just not sure how folks are doing that - what works? what doesn't?
Brian
