@@ -58,6 +58,8 @@ The following pattern is used when merging with `extends`:
5858
5959Name files according to the following patterns to make searching in future more easy:
6060
61+ <!-- {% raw %} -->
62+
6163#### Test file name
6264
6365Format: {_ Admin_ or _ Storefront_ }{Functionality}_ Test.xml_ , where Functionality briefly describes the testing functionality.
@@ -80,6 +82,8 @@ Example: _AdminNavbarSection.xml_.
8082
8183Format: {Type}_ Data.xml_ , where Type represents the entity type.
8284
85+ <!-- {% endraw %} -->
86+
8387Example: _ ProductData.xml_ .
8488
8589### Object names
@@ -91,18 +95,18 @@ Use the _Foo.camelCase_ naming convention, which is similar to _Classes_ and _cl
9195Use an upper case first letter for:
9296
9397- File names. Example: _ StorefrontCreateCustomerTest.xml_
94- - Test name attributes. Example: ` <test name="TestAllTheThingsTest"> ` .
95- - Data entity names. Example: ` <entity name="OutOfStockProduct"> ` .
96- - Page name. Example: ` <page name="AdminLoginPage"> ` .
97- - Section name. Example: ` <section name="AdminCategorySidebarActionSection"> ` .
98- - Action group name. Example: ` <actionGroup name="LoginToAdminActionGroup"> ` .
98+ - Test name attributes. Example: ` <test name="TestAllTheThingsTest"> `
99+ - Data entity names. Example: ` <entity name="OutOfStockProduct"> `
100+ - Page name. Example: ` <page name="AdminLoginPage"> `
101+ - Section name. Example: ` <section name="AdminCategorySidebarActionSection"> `
102+ - Action group name. Example: ` <actionGroup name="LoginToAdminActionGroup"> `
99103
100104#### Lower case
101105
102106Use a lower case first letter for:
103107
104- - Data keys. Example: ` <data key="firstName"> ` .
105- - Element names. Examples: ` <element name="confirmDeleteButton"/> ` .
108+ - Data keys. Example: ` <data key="firstName"> `
109+ - Element names. Examples: ` <element name="confirmDeleteButton"/> `
106110- Step keys. For example: ` <click selector="..." stepKey="clickLogin"/> `
107111
108112## Page object
0 commit comments