RSS Feed

Axe Test Automation Platform

Hi,

Could you please let me know the max limit of rows / columns for a good axe test system the below:

1. ObjectMap Table

2. Sub Test Table

3. Test Table

4. Run Table
Thanks
Smita

adding some info to the question above,

I've tried to create a subtest from an objectmap which contains 200 rows. It prompted me saying that the max limit allowed is 126 objects only and causing to create another subtest for remaining 74 objects.

Could you please let me know that is there any possibility to increase this number in the object map in the latest release available..


smita

Hi Smita,

The limits you talk about are the limits provieded by Excel as each of these table types are worksheets in Excel. For each of the categories:

1. Object Maps -

A) The number of objects/windows - this is dictated by the depth of the table, in Excel 2003 - 65536 - 1 (header) = 65535 objects.
B) The number of properties is the width of the worksheet - 256 - 2 (name and class) = 254 property columns.

2. Sub Test - (The subject of your question)

A) The number of steps = 256 - 3 (header) 253 / 2 (step needs 2 columns) = 126 steps.

B) Subtest rows = 65536 - 2 (header) = 65534

We generally recommend a subtest per page/window. If you find you a breaching the size of subtests, it is worth thinking about breaking a larger window into subsections for maintainability. We rarely find the contraints in Excel troublesome.

3. Test Tables

A) The number of subtests in a test sequence = 256 - 4 (header) = 252/2 (subtest ref needs 2 columns) = 126 subtests.

B) The number of tests = 65536 - 1 = 65535

These limits have not been hit on commercial systems we are aware of. Again you can split a test in two if it breaches the number of subtests, although again I would question the length of such a test and should it be a series of smaller tests.

4. Run Table

A) Only rows count in this so - 65535.

Hope this helps.

Did the information above help? Please contact support@odin.co.uk with your details if you need anything further.

Many Thanks,

Duncan