RSS Feed

Axe Test Automation Platform

I have a few questions to ask, which may inform which direction we take as far as automation is concerned. We need to be able to test the same application functionality in multiple browsers, e.g. IE and Firefox, and potentially multiple versions.

1) Is there any news on the integration of WatiN 2.0 with Axe? I understand it is still in Beta at the moment, but a timescale/way forward on this would be great.

2) Where cross browser testing is required, would it be beneficial to have seperate test repositories (for objectmaps, actionmaps, tests etc) for each browser we are testing. I understand from reading the SQA Forums that the way some browsers are handled by the same test tool is different, e.g IE objects are handled differently to Firefox objects.

Any comments?

Hi Daniel,

1. WatiN 2.0 support in Axe.
At the moment we cannot provide a definite date because WatiN 2.0 is still in Beta. We cannot complete the Axe support until WatiN 2.0 has been finalised. The WatiN website does not currently indicate when this will be. I would therefore guess that the official Axe integration is a few months off although a version that works with the WatiN 2.0 beta could be made available sooner, depending on the individual case.
The WatiN roadmap is at http://watin.sourceforge.net/roadmap.html but it hasnt been updated for a while.

2. Multiple browsers.
The strategy will ultimately depend on which tool you are using and wether you are using a native or Axe format object map. You may need multiple maps for each browser and some action map updates but the tests themselves should not need any changes. You may also want to customise your basestate functions to pick-up a run config option that determines the choice of browser.

Sam