RSS Feed

Axe Test Automation Platform

We are struggling to use Axe in a multi-tester enviroment.

We've setup SVN for the project but are getting complaints that checking in test sheets is a pain.

The merge causes a problem when someone has added a sub test to a sheet that includes a new object coloumn.
The line can be merged but the other existing tests don't have a hash in the, now empty fields, and therefore fail to build.

Is anyone else using Axe in a multi-user enviroment and if so any tips?

Thanks
Russ

Hi Russ,

It sounds like your challenge here is the configuration and practices of your version control system, and even convincing your users this is the best thing! For our clients, our typical team size is between 5-10 users, with a number upward of 20. Most developers are used to working with Version control systems and know that there is no other way to develop. It is often a challenge to convince non-developers of the need for version control systems until something goes wrong, then they are converts!
SVN is a very flexible Version control system that allows users to work on the same file and then merge results. I however wouldn't recommend using the Merge facility at all on XML files or any binary files as it can lead to corruption, Merging is better applied to source code files and even then it leads to issues. You can apply configuration settings to SVN to lock files that are being used (similarly to VSS and TFS), perhaps this is best applied to your environment.

Another good tip, is that when working in a multi user environment it is important to split up the workbooks into manageable and maintainable chunks and use the ability of Axe to link to other workbooks. I would recommend breaking an application into smaller functional units and keeping the subtests for each in a seperate workbook, also use a seperate workbook for common navigation, login etc.

Hope this is of some help.

Duncan