Naming conventions for Java based Test Automation Framework

Hello QA Enthusiasts,

Scaling a Test Automation Frameworks require different factors, one such crucial factor is managing “Naming Conventions”. This one helps our code to be readable and reduces code complexity.

Why Naming conventions matter?

1) Consistent naming conventions helps in code readability and makes it easier for whole team to understand the code base.

2) Maintenance becomes easier, as we can easily understand where the dependencies, constants etc. needs to be updated.

3) Newer team members, can go through the code base directly and do not require to get a documentation or discussion with other team members.

Naming Conventions for

Packages:

Keep all package names in lowercase, separated by periods (.). Start with your company’s domain in reverse, followed by clear and concise module names.

Example:

com.automationtech.test.pages
com.automationtech.test.utils

Classes: