Naming Conventions While Creating Custom Actions

Choosing Names for Action Words in Custom Actions

When creating custom actions, particularly those representing specific functionalities, it's crucial to select names that are descriptive and clearly communicate their purpose.

Follow these guidelines to ensure your custom action names are clear, meaningful, and consistent:

• Be Descriptive: Choose names that clearly describe the action performed by the method. Avoid ambiguous names that might lead to confusion.
  
  
• Be Consistent: Maintain consistency in naming across your custom action. If you have similar actions, use similar naming patterns. For example, if you have methods for clicking buttons, ensure they all start with "Click."
  
  
• Avoid Abbreviations: Avoid abbreviations that may not be immediately understandable to other testers. Opt for complete words that provide clarity and reduce ambiguity. For example, choose "Initialize" over "Init," unless the abbreviation is widely recognized and used in your domain.

Example

Consider the example of performing a user authentication scenario using a custom action named 'log onto Ecommerce website'. This action consolidates the necessary steps for user authentication, including entering the user's name and password and clicking the submit button. By following the guidelines when creating custom actions, you ensure that your action names are clear, meaningful, and consistent. This consistency promotes efficient test case design and execution.