Best practices | TestCases | Names

Typically, you create a new TestCase and then use Modules to add your TestSteps.

It's incredibly important to choose good names for TestCases and TestSteps. Good names give you important facts at a glance: what a TestCase is about, what exactly happens in it, and which TestCase in a folder or search result is the one. It's even more important when it comes to reporting and analyzing results, where you need to understand quickly what worked—and what didn't.

So, don't do this:

Instead, follow the naming conventions we've outlined here. 

TestCase names

Each TestCase needs a unique name that explains the purpose of the TestCase. If you test multiple applications, also add the application name.

TestStep names

Each TestStep needs an action-oriented name.

By default, Tosca uses the name of the Module for the TestStep, but that doesn't work in TestCases. Good Module names are about controls and their location.

In your TestCase, however, you need to know what exactly happens in this particular instance and where. Rename your TestSteps, so that they have this information.

What's next

If you haven't yet, check out our other best practices articles.