Replaced {% raw %} blocks.

Author: dobooth

docs/best-practices.md

@@ -1,7 +1,5 @@
 # Best practices
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 Check out our best practices below to ensure you are getting the absolute most out of the Magento Functional Testing Framework.
 
 ## Action group
@@ -109,10 +107,14 @@ Do not use them for static elements.
 BAD:
 </span>
 
+<!-- {% raw %} -->
+
 ``` xml
 <element name="relatedProductSectionText" type="text" selector=".fieldset-wrapper.admin__fieldset-section[data-index='{{productType}}']" parameterized="true"/>
 ```
 
+<!-- {% endraw %} -->
+
 <span class="color:green">
 GOOD:
 </span>
@@ -146,19 +148,19 @@ Since the configurable product module could be disabled, this approach is more r
 
 <!-- Link definitions -->
 
-[`<after>`]: test/actions.html#before-and-after
-[`<before>`]: test/actions.html#before-and-after
-[`<comment>`]: test/actions.html#comment
-[`<createData>`]: test/actions.html#createdata
-[`<deleteData>`]: test/actions.html#deletedata
-[`<wait>`]: test/actions.html#wait
-[`<waitForElement>`]: test/actions.html#waitforelement
-[`<waitForElementVisible>`]: test/actions.html#waitforelementvisible
-[`<waitForLoadingMaskToDisappear>`]: test/actions.html#waitforloadingmasktodisappear
-[Action group]: test/action-groups.html
-[annotations]: test/annotations.html
-[entity]: data.html
-[extension]: extending.html
-[merging]: merging.html
-[parameterized selectors]: section/parameterized-selectors.html
-[sections]: section.html
+[`<after>`]: test/actions.md#before-and-after
+[`<before>`]: test/actions.md#before-and-after
+[`<comment>`]: test/actions.md#comment
+[`<createData>`]: test/actions.md#createdata
+[`<deleteData>`]: test/actions.md#deletedata
+[`<wait>`]: test/actions.md#wait
+[`<waitForElement>`]: test/actions.md#waitforelement
+[`<waitForElementVisible>`]: test/actions.md#waitforelementvisible
+[`<waitForLoadingMaskToDisappear>`]: test/actions.md#waitforloadingmasktodisappear
+[Action group]: test/action-groups.md
+[annotations]: test/annotations.md
+[entity]: data.md
+[extension]: extending.md
+[merging]: merging.md
+[parameterized selectors]: section/parameterized-selectors.md
+[sections]: section.md

docs/credentials.md

@@ -64,6 +64,8 @@ carriers_usps_password=Lmgxvrq89uPwECeV
 ....
 ```
 
+<!-- {% raw %} -->
+
 ## Use credentials in a test
 
 Access the data defined in the `.credentials` file using the [`fillField`][] action with the `userInput` attribute.
@@ -78,6 +80,8 @@ For example:
 <fillField stepKey="FillApiToken" selector=".api-token" userInput="{{_CREDS.my_data_key}}" />
 ```
 
+<!-- {% raw %} -->
+
 ## Implementation details
 
 The generated tests do not contain credentials values.

docs/data.md

@@ -1,12 +1,12 @@
 # Input testing data
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 The MFTF enables you to specify and use `<data>` entities defined in XML. Default `<data>` entities are provided for use and as templates for entity creation and manipulation.
 The following diagram shows the XML structure of an MFTF data object:
 
 ![MFTF Data Object](img/data-dia.svg)
 
+<!-- {% raw %} -->
+
 ## Supply data to test by reference to a data entity
 
 Test steps requiring `<data>` input in an action, like filling a field with a string, may reference an attribute from a data entity:
@@ -166,6 +166,8 @@ The following is an example of a call in test:
 <fillField selector="{{AdminCategoryBasicFieldSection.categoryNameInput}}" userInput="{{_defaultCategory.name}}" stepKey="enterCategoryName"/>
 ```
 
+<!-- {% endraw %} -->
+
 This action inputs data from the `name` of the `_defaultCategory` entity (for example, `simpleCategory598742365`) into the field with the locator defined in the selector of the `categoryNameInput` element of the `AdminCategoryBasicFieldSection`.
 
 ## Reference

docs/extending.md

@@ -20,6 +20,8 @@ Unlike merging, the parent test (or action group) will still exist after the tes
 
 ### Update a test step
 
+<!-- {% raw %} -->
+
 __Use case__: Create two similar tests with different `url` (`"{{AdminCategoryPage.url}}"` and `"{{OtherCategoryPage.url}}"`) in a test step.
 
 > Test with "extends":
@@ -281,6 +283,8 @@ Add a new test `VerifyProductCount` that asserts the count of products:
 </actionGroups>
 ```
 
+<!-- {% endraw %} -->
+
 ## Extending data
 
 Extend data to reuse entities in your module.

docs/merging.md

@@ -45,6 +45,8 @@ Learn more about running tests with different options using [`mftf`] or [`codece
 
 Skip the `AdminLoginTest` test in the `.../Backend/Test/AdminLoginTest.xml` file while merging with the `.../Foo/Test/AdminLoginTest.xml` file:
 
+<!-- {% raw %} -->
+
 ```xml
 <tests ...>
     <test name="AdminLoginTest">
@@ -304,6 +306,8 @@ The controls change drastically in the B2B version, so it was abstracted to an a
 </actionGroup>
 ```
 
+<!-- {% raw %} -->
+
 ## Merge pages
 
 Use [page] merging to add or remove [sections] in your module.

docs/page.md

@@ -13,6 +13,8 @@ Avoid hard-coded location selectors from tests to increase the maintainability a
 
 Two types of pages are available:
 
+<!-- {% raw %} -->
+
 - Page with `url` declared as a constant string or [explicit page] - In a test it is called in a format like `{{NameOfPage.url}}`, where `NameOfPage` is a value of `name` in the corresponding page declaration `*.xml` file.
 - Page with `url` declared as a string with one or more variables or [parameterized page]
 - In a test it is called using a format like `{{NameOfPage.url(var1, var2, ...)}}`, where `var1, var2` etc. are parameters that will be substituted in the `url` of the corresponding `<page>` declaration.
@@ -148,6 +150,8 @@ Attributes|Type|Use|Description
 
 `<page>` may contain several [`<section>`] elements.
 
+<!-- {% endraw %} -->
+
 ### section {#section-tag}
 
 `<section>` contains the sequence of UI elements.

docs/section.md

@@ -6,6 +6,8 @@ A `<section>` is a reusable part of a [`<page>`](./page.md) and is the standard
 
 A `<section>` can define:
 
+<!-- {% raw %} -->
+
 - An explicit element that has a selector equal to the constant string. Example: `selector="#add_root_category_button"`
 - A parameterized element that contains substitutable values in the selector. Example: `selector="#element .{{var1}} .{{var2}}"`.
 
@@ -132,6 +134,8 @@ The test step that covers the use case:
 ...
 ```
 
+<!-- {% endraw %} -->
+
 Whenever the `signIn` button is used in a test, the MFTF will add a 30 second `waitForPageLoad` action immediately after the `click`.
 
 <!-- Link definitions -->

docs/section/locator-functions.md

@@ -20,6 +20,8 @@ When using the `locatorFunction`, omit `Locator::` for code simplicity:
 
 An element's `locatorFunction` can also be parameterized the same way as [parameterized selectors][]:
 
+<!-- {% raw %} -->
+
 ```xml
 <element name="simpleLocatorTwoParam" type="button" locatorFunction="contains({{arg1}}, {{arg2}})" parameterized="true"/>
 ```
@@ -37,6 +39,8 @@ Given the above element definitions, you call the elements in a test just like a
 </test>
 ```
 
+<!-- {% endraw %} -->
+
 <!-- Link Definitions -->
 [Locator functions]: http://codeception.com/docs/reference/Locator
 [section]: ../section.md

docs/section/parameterized-selectors.md

@@ -30,6 +30,8 @@ Add your selector in the `selector=""` attribute:
 </section>
 ```
 
+<!-- {% raw %} -->
+
 ### Selector with single variable
 
 For the parameterized part of the selector, add `{{var1}}` to represent the first piece of data that you want to replace:
@@ -142,6 +144,8 @@ Add the second or third parameters, that you'd like to pass to the selector, sep
 </test>
 ```
 
+<!-- {% endraw %} -->
+
 Any data can be used in parameterized elements, as well as entered in test actions:
 
 * `_defaultCategory.is_active` is a reference to `<data key="is_active">` in `<entity name="_defaultCategory" ... ></entity>` in the corresponding `.../Data/*.xml`.

docs/test/action-groups.md

@@ -54,6 +54,8 @@ To create the `<actionGroup>` declaration:
     </actionGroups>
     ```
 
+<!-- {% raw %} -->
+
 1. Add actions to the `actionGroup` arguments:
 
     ```xml
@@ -219,6 +221,8 @@ It can be reworked into more manageable pieces, as below. These smaller steps ar
 </actionGroup>
 ```
 
+<!-- {% endraw %} -->
+
 ## Elements reference
 
 ### actionGroups {#actiongroups-tag}