Name & Description

1. Functionalities should be named in a manner that enables easy identification of the corresponding functional requirement or scenario, for which the functionality is written. The Onlooker should be able to trace the functionality back to the requirement or Scenario by the name of the functionality.

Example 1, an Action written or recorded for logging the user should be named as Login or Authentication for easy understandable.

Example 2, if each test requirement is associated with one functionality and the name of the functionality is ‘Create a new Colleague’ then the functionality name would be 'Add Colleague', and associated test cases names would be - Add Colleague.xlsx, Add Colleague_Filed level.xlsx, & Add Colleague_Element Checks.xlsx etc.

2. Functionality description should be described with detailed functional flow information about test subject.

3. Typically Actions are segregated by their functionality in the Test Script. Therefore it would be easier to understand the Action if the description of the action represents the Functionality. This can provide clarity and difference between a Reusable Action and a Function that can be used within Actions.