Test case names convention

[ohenneberg]

Hi,

We have just startet typing in new test suites and test cases in our organisation, but have ran into the question how we should handle the naming convention for our testcases.

Do any of you have some good experience of how to do the naming part, do you use the default testlink numbering like, "NG-101 Create text", "NG-102 Delete text", or have you bypassed the default option and setup that you do'nt want Testlink to show the default numbering?

We have tried to change the setup, so we hide the default numbering of test cases, and startet giving the cases our own numbering, like "1-1.1 Create Text", "1-2.2 Delete Text", but wonder if that will work for us? We thought that the numbering should help us with the order of the test cases, but ran into that it proberly not will work for us, because we will have to add new test cases in between existing ones all the times.

So maybe we should "just" jump back to the default test case naming in testlink and dont spend so much time on having our own index numbering in front of the test cases? Maybe testlink it's good enough to handle the order of test cases, that we do'nt need the index part of the test case names?

THANKS for any feedback on your experence with this in Testlink!

Ole

[gianmaria]

Hi,
personally I use the standard naming convention of TL.
I use the project, so the prefix change.
Example:

Project trial.
test case: TRIAL-1100-<short description>_<sequence> -->> TRIAL-1100-new font size UI_001. TRIAL-1101-new font size UI_002

After that we group the test cases in test suite, like "new UI"

[ohenneberg]

THANKS gianmaria!

Default my testlink installation, make the first test case with the identifier NG-<sequence>+<short description>, but when I look at your example, you get the <sequence> number as the last part of the identifier!
How or where have you changed that setup?

[fman]

1. TestLInk does not have any mechanisim to force a naming convention on test cases (and in any other item you can create: Test Project, Test Suite, Req. Spec, Requirement).

2.TestLink mantains for each test project a test case counter, that is only increased (never decrease) any time a test case is created.
Value of this counter is used with Test project prefix, to generate what in TestLink is know as 'External Test Case Id'.

3. External Test Case ID is not part of Test Case Name.
4. In every TestLink feature, if External Test Case ID is displayed, it's always displayed to the LEFT of Test Case Name.

IMHO:
Trying to use an Internal Guide line for naming convention that use some kind of numbering scheme, will only produce lot of useless work. (who is going to change names any time a test case is added or deleted ?)
People (customers and managers) have to be persuaded that the attributes that makes a good test case are :

a. Good and clear title, that in few words allows the person to graps the scope/target
b. Very good test case design (level of details used, qty and value of information provided).

Having all test cases with a monotonic numbering inside each Test suite provide no value, and is a mantainance nightmare.

[ohenneberg]

Thanks!

And would recommend the same for the Test suite naming? (not adding any numbering, but just a plain text name)

[gianmaria]

THANKS gianmaria!

Default my testlink installation, make the first test case with the identifier NG-<sequence>+<short description>, but when I look at your example, you get the <sequence> number as the last part of the identifier!
How or where have you changed that setup?

Hi.
We add manually the sequence ad the end. For our convenience. Just to group tests with the same "coverage area".