Worksoft Certify Naming Convention – Best Practices

In the Worksoft Automated Testing methodology, a naming standard consists of rules that specify how to name Folders, Processes, Variables, Layouts and Recordsets within the Worksoft Certify test automation toolset.

A good naming standard brings order and reduces confusion, especially in shared Certify environments.

Consistent naming helps users quickly understand entities, making maintenance easier. As test assets grow, clear naming ensures future analysts and developers to efficiently manage, reuse, and adapt processes for evolving business needs.

Why is a Naming Convention Essential?

Adopting standardized naming conventions in Worksoft Certify is essential for ensuring clarity, consistency, and maintainability within automation frameworks. Here’s why following best practices for naming conventions is crucial:

• Clarity & Readability – A structured naming convention makes test scripts easy to understand, reducing confusion among team members.
• Collaboration – A consistent naming approach ensures smooth teamwork, allowing multiple testers to work efficiently without misinterpretation
• Maintainability – Well-named processes and test cases help to quickly identify and update specific components without unnecessary effort.
• Standardization Across Teams – A well-defined naming standard ensures consistency across different projects and teams, making onboarding and knowledge transfer easier.
• Improved Reporting & Analysis – Meaningful names help generate clear and structured test execution reports, making it easier to analyze test results.
• Version Control & Auditing – A structured naming system makes it easier to track changes, maintain version history, and comply with audit requirements.
• Integration with Other Tools – When integrating Worksoft Certify with other automation or reporting tools, consistent names simplify data mapping and processing.

Worksoft Certify Best Practices for Naming Consistency

Following best practices, the process name, record set, and layout name should be identical to ensure clarity, minimize confusion, and enhance usability for all users.

Before going further, we highly suggest you read our comprehensive blog on Folder Structures!

Folder Structures

A well-organized folder structure in Worksoft Certify is crucial for managing test assets efficiently. It helps users quickly locate, reuse, and maintain Processes, Layout and Recordsets, results etc.

Now, let’s go step by step through the naming conventions for different processes in Worksoft Certify.

Integrated / End-to-End Processes

Integrated or E2E processes contain calls to other processes that include Transactional Processes, Child Processes, Utilities, Comments, Variables initialization, swaps and other steps that may be required for the integrated components.

When implementing the Integrated/End-to-End Test Processes naming convention, separate test names and descriptions with an underscore.

Remove spaces from descriptions and capitalize the first letter of each word to closely match the manual test case name.

By following this naming convention, you ensure that integrated processes are clearly defined, easy to locate, and consistent across teams.

Syntax:

ApplicationArea_Description1_Description2_Description3

Example: 

SAPSuccessFactors_Employee_ApplyLeaveOfAbsense_LOA

Transactional and Child Process

Transactional tests are component scripts developed and stored in their respective folders.

 Child processes are sub-Transactional processes created to iteratively input data into tables, group complex logics and to group similar steps to avoid ambiguity.

• Naming Convention for Transactional Process

When implementing the naming convention for transactional processes, separate test names and descriptions with an underscore.

Remove spaces from descriptions and capitalize the first letter of each word.

SAP GUI Syntax: 

TCODE_Description1_Description2_Description3

Example:

VA01_CreateSalesOrder

Non-SAP GUI Syntax:

Application_Description1_Description2_Description3

Example:

SAPAriba_Invoice_CreateInvoice

• Naming Convention for Child Process

When naming a child process, it must start with the name of the parent processes separated by an “_C_”, followed by the description separated by an underscore.

Syntax:        

ParentTransactionalProcess_C_Description1_Description2_Description3

Example:  

VA01_CreateSalesOrder_C_InputLineItems

• Naming Convention for SAP HR Info Types TCodes

In SAP GUI, when naming SAP HR transactional processes such as PA30 and PA40, it is recommended to include the Info Types along with the standard naming convention shown above.

Syntax:        

TCODE_IT<InfoTypeNo>_InfoTypeText_Country/State

Examples:    

PA40_IT0009_BankDetails_IN

PA40_IT0068_PensionFunds_GB

Utilities

Utilities store reusable components such as generic functions and actions that can be used across multiple tests, like closing browsers.

They help organize common tasks, promote consistency, reduce redundancy, and simplify maintenance by enabling updates in one place to reflect across all tests that utilize these utilities.

When naming Worksoft Utilities, it’s essential to follow a consistent convention for clarity and organization. The names should be capitalized, with descriptions separated by underscores to clearly define each part.

Being descriptive is key to ensuring the utility’s purpose and functionality are easily understood.

Syntax:        

UTL_ Description1_Description2_Description3

Examples:    

UTL_SAPGUI_Launch

UTL_Salesforce_Logout

UTL_Date_GetLastWorkingDayOfCurrentMonth

Layout

A Layout in Worksoft Certify is a collection of one or more project variables, serving as a blueprint for the data supplied through Recordsets.

When implementing the Data Layouts naming convention, the layout names should match the process name to which the layout is tied or attached to.

Syntax:        

Same as the attached process name

Examples:    

SAPSuccessFactors_Employee_ApplyLeaveOfAbsense_LOA

VA01_CreateSalesOrder

VA01_CreateSalesOrder_C_InputLineItems

For Variant Layouts, the name will be the same as the Process name with an added identifier. This ensures consistency and easy identification of the layouts associated with their respective processes.

Syntax:        

Same as the attached process name but with some variations

Example:    

Process Name = MM01_CreateMasterData

Primary Layout Name = MM01_CreateMasterData

Secondary Layout Name = MM01_CreateMasterData_3rdPartyData

Recordsets

Recordsets are subsets of a Layout that contain the same defined variables, enabling structured data management for test execution. To maintain clarity and consistency, it is best to name Recordsets after the associated process name.

Additionally, multiple Recordsets can be used within a single test to accommodate different data variations.

Syntax: Same as Process Name, Layout and with variation

Example:    

Process Name = VA01_CreateSalesOrder

Layout Name = VA01_CreateSalesOrder

Recordset Name = VA01_CreateSalesOrder_0045_IN

Recordset Name = VA01_CreateSalesOrder_0067_US

Variables

Certify Variables hold data during the process execution and correspond to fields displayed on the screen.

Use existing variables whenever possible to avoid clutter in the variable folder and ensure easier debugging.

Only create new variables when no suitable existing one is available.

When creating variables, it is recommended to use consistent naming conventions like below.

Syntax:        

Should closely match field names

Example:    

Order Type, Ship-to Party, First Name, Delivery

If the field name is “Del date”, then make use of an existing variable “Delivery Date” instead of creating a new one.

If multiple variables are needed, append a “_<VariantName>” or a “_<FormatType>”

Syntax:        

VariableName_FormatType/VariantName

Example:    

Req. deliv.date_Date

For creating duplicate variables, use a “#” to differentiate them like below

Syntax:

VariableName_#<No>

Example:    

Customer#1, Customer#2

Conclusion

Having a clear and consistent naming convention in Worksoft Certify makes test automation easier to manage, update, and understand. It helps teams work together better, reduce mistakes, and improve reporting.

By following standardized naming rules, workflows become more efficient, and automation processes remain well-organized. Using these best practices ensures a smoother experience for everyone working on test automation projects.