Katalon-UI test code naming convention

Katalon-UI test code naming standard
When implementing UI automatic test code projects on Katalon, a unified naming standard is required. Everyone writes automatic test code according to this standard.
The Katalon project hierarchy is as follows:
——Profiles-level
profile_module name/project name_XX, such as profile_project_ui, profile_project_api
default: global files, rename, modify and delete
Multiple profile files are allowed to be added, and the new
role of rename and delete operations is allowed : Mainly used to store the URL address of the test running environment, the database connection account, the login test address, the global account-
TestCases level
(1) Create a new first-level directory: tc_tag_first-level module name/project name/feature name, unified Lower case, such as tc_project_projectname or tc_feature_featurename
(2) Second-level directory: If you need to refine the sub-modules under the first-level directory, module_second-level module name, unified lowercase
(3) Third-level directory: divided into 2 Two parallel levels-
Pages: Mainly used to store some operation steps in each module page (can be understood as some execution steps in test cases)
For example: Login_Pages
------Tests: Call some operations under Pages Assemble into corresponding test cases (combine and encapsulate the execution steps into test cases with business scenarios)
——Object Repository level
(1) Create a new first-level directory: obj_tag (such as UI/feature)_first-level module name/ Project name/feature name, uniformly lowercase
(2) Second-level directory: If the first-level directory still needs to be refined to sub-modules, module_second-level module name, unified lowercase
(3) Third-level directory: control object naming rules, control type_control Name
text box: tbox_ element name in English (small hump);
traditional button: btn_ element name in English (small hump);
picture button: ibtn_ element name in English (small hump);
text button: tbtn_ element name in English ( Small hump);
drop-down box: dbtn_ element name in English (small hump);
check box: cbtn_ element name in English (small hump);
radio box: rbtn_ element name in English (small hump);
scroll bar: sbar_ Element name in English (small hump);
——TestSuite level
Create a new first-level directory: ts_tag (such as UI/feature)_project name/feature name, uniformly lowercase
(2) Second-level directory: if the first-level directory Next, you need to refine the sub-modules, module_second-level module name, unified lowercase
(3) third-level directory: use case set business scenario _all/part_priority1/2 or
Smoke/Regression_UI_test
——DataFiles level
(1) new First-level directory: tag_first-level module name/project name/feature name, uniformly lowercase, such as project_projectname or feature_featurename
(2) Second-level directory: If you need to refine sub-modules under the first-level directory, module_ secondary module name, uniformly lowercase
(3) File name: label (excel/csv/db/innal)_filename
——Keywords level
(1) First-level directory: com.XXXX (company identification name)
(2) Second-level directory: encapsulate and define public methods such as operating databases, operating files, etc.