5.2.1 Naming conventions for Test Cases

You should name your Test Cases so that it is clear from the name what the Test Case does. Instead of vague or ambiguous names (e.g. Select), try and write names that describe the Test Case in terms of the action and the component it deals with. A few good examples are:

The Test Case names do not have to exhaustively describe the component, or where it is in the AUT - using categories for the different areas of your AUT saves you having to do this 5.3.1. The aim with naming your Test Cases is to make your tests readable and easy to understand.

You do not have to write Test Case names in CamelCase or with underscores - Test Case names are not used in the test executor, so there is no problem if they have spaces in them.



Copyright BREDEX GmbH 2012. Made available under the Eclipse Public License v1.0.