View source | Discuss this page | Page history | Printable version   

ERP 2.50:Automated Testing/Test Identifiers

Every automated test must have a unique identifier, so we can refer to it on an easy way.

The identifier should at least give a clue about the test and it should follow the order of the tests on the suite they belong to.

So, for every suite we will define a three letter identifier that makes sense with the name of the module. For example, we have ADM for Administration master data suite, and PRJ for Project and service management suite.

If you are not sure if the identifier for your suite was already taken, please consult with a member of the QA team.

Then, the tests that form part of that suite will be identified by the three letters of the suite plus four digits. But the four digits will be a sequence of numbers from ten to ten. Thus, the first test of Project and service management suite will be identified by PRJ0010 and the second by PRJ0020.

This weird numbering sequence is required because it's very common to add some tests in the middle of suite. If we numbered tests from one to one (PRJ0001 and PRJ0002 in the previous example) and we need to insert a test between two of them, there's no straightforward way to keep the numbering sequence.

But, if we follow the ten to ten rule and we need to add a test between the first and the second test, it would be easily identified by 'PRJ0015. And every time that a test suites gets to a stable phase, the tests will be renumbered so the newly added tests get a distance of 10 numbers from their previous and next tests.

On testlink, tests will be named [XXX####] Name of the test and on the automated test scenarios they will be named XXX####_NameOfTest.

Retrieved from ""

This page has been accessed 5,626 times. This page was last modified on 3 April 2012, at 11:00. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.