Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
31 changes: 31 additions & 0 deletions guides/v2.2/coding-standards/technical-guidelines.md
Original file line number Diff line number Diff line change
Expand Up @@ -715,6 +715,37 @@ You need to read configuration from different sources (like database or filesyst

11.2.3. `ObjectManagerHelper` MAY BE used to automatically mock all dependencies of the object under test.

### 11.3. Functional Testing

#### 11.3.1. Pages

11.3.1.1. Page file names MUST follow this pattern:

* {Admin or Storefront}{Description}Page.xml, where {Description} briefly describes the page under test.
* Use [PascalCase](http://wiki.c2.com/?PascalCase).
* Example: AdminProductAttributeGridPage.xml

11.3.1.2. Page `name` attribute MUST be the same as the file name.

11.3.1.3. Page `module` attribute MUST follow this pattern:

* {VendorName}_{ModuleName}
* Example: Magento_Backend

11.3.1.4. There MUST be only one `<page>` entity per file.

#### 11.3.2. Sections

11.3.2.1. Section file names MUST follow this pattern:

* {Admin or Storefront}{Description}Section.xml, where {Description} briefly describes the section under test.
* Use [PascalCase](http://wiki.c2.com/?PascalCase).
* Example: StorefrontCheckoutCartSummarySection.xml

11.3.2.2. Section `name` attribute MUST be the same as the file name.

11.3.2.3. There MUST be only one `<section>` entity per file.

## 12. Web API

12.1. Both REST and SOAP API's MUST be exposed.
Expand Down