Change a lot of code as we move MFTF docs to new repo.

Author: dobooth

docs/best-practices.md

@@ -1,12 +1,6 @@
----
-mftf-release: 2.3.0
-redirect_from: /guides/v2.3/magento-functional-testing-framework/2.3/best-practices.html
----
-
 # Best practices
 
-_This topic was updated due to the {{ page.mftf-release }} MFTF release._
-{: style="text-align: right"}
+<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.
 
@@ -111,15 +105,17 @@ Use a lower case first letter for:
 Use [parameterized selectors] for constructing a selector when test specific or runtime generated information is needed.
 Do not use them for static elements.
 
-{:style="color:red"}
+<span class="color:red">
 BAD:
+</span>
 
 ``` xml
 <element name="relatedProductSectionText" type="text" selector=".fieldset-wrapper.admin__fieldset-section[data-index='{{productType}}']" parameterized="true"/>
 ```
 
-{:style="color:green"}
+<span class="color:green">
 GOOD:
+</span>
 
 Define these three elements and reference them by name in the tests.
 

docs/commands/codeception.md

@@ -1,16 +1,10 @@
----
-mftf-release: 2.3.0
-redirect_from: /guides/v2.3/magento-functional-testing-framework/2.3/commands/codeception.html
----
-
 # CLI commands: vendor/bin/codecept
 
-_This topic was updated due to the {{page.mftf-release}} MFTF release._
-{: style="text-align: right"}
+<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
 
-{:.bs-callout .bs-callout-warning}
+<span class="bs-callout bs-callout-warning">
 We do not recommend using Codeception commands directly as they can break the MFTF basic workflow.
-All the Codeception commands you need are wrapped using the [`mftf` tool][].
+All the Codeception commands you need are wrapped using the [`mftf` tool][].</span>
 
 To run the Codeception testing framework commands directly, change your directory to the `<Magento root>`.
 
@@ -42,8 +36,9 @@ vendor/bin/codecept run functional --group example --skip-group skip
 vendor/bin/codecept run
 ```
 
-{: .bs-callout .bs-callout-info }
+<span class="bs-callout .bs-callout-info"
 The following documentation corresponds to Codeception 2.3.8.
+</span>
 
 ```bash
 Full reference:
@@ -70,7 +65,7 @@ Options:
    --coverage-xml        Generate CodeCoverage XML report in file (default: "coverage.xml")
    --coverage-text       Generate CodeCoverage text report in file (default: "coverage.txt")
    --coverage-phpunit    Generate CodeCoverage PHPUnit report in file (default: "coverage-phpunit")
-   --no-exit             Don't finish with exit code
+   --no-exit             Do not finish with exit code
    --group (-g)          Groups of tests to be executed (multiple values allowed)
    --skip (-s)           Skip selected suites (multiple values allowed)
    --skip-group (-x)     Skip selected groups (multiple values allowed)
@@ -87,5 +82,5 @@ Options:
 
 <!-- Link definitions -->
 
-[`mftf` tool]: mftf.html
-[annotation]: ../test/annotations.html
+[`mftf` tool]: mftf.md
+[annotation]: ../test/annotations.md

docs/commands/mftf.md

@@ -1,20 +1,10 @@
----
-mftf-release: 2.3.11
-redirect_from: /guides/v2.3/magento-functional-testing-framework/2.3/commands/mftf.html
----
-
 # CLI commands: vendor/bin/mftf
 
-_This topic was updated due to the {{page.mftf-release}} MFTF release._
-{: style="text-align: right"}
+<span class="style="text-align: right"">_This topic was updated due to the 2.3.13 MFTF release._</span>
 
 The Magento Functional Testing Framework (MFTF) introduces the command line interface (CLI) tool `vendor/bin/mftf` to facilitate your interaction with the framework.
 
-{%
-include note.html
-type='info'
-content='`mftf` commands replace the `robo` commands that were used in previous releases.'
-%}
+Note that `mftf` commands replace the `robo` commands that were used in previous releases.
 
 ## Command format
 
@@ -179,10 +169,7 @@ The command that encodes this complex configuration:
 vendor/bin/mftf generate:tests --tests "{\r\n\"tests\":[\r\n\"general_test1\",\r\n\"general_test2\",\r\n\"general_test3\"\r\n],\r\n\"suites\":{\r\n\"sample\":[\r\n\"suite_test1\"\r\n],\r\n\"sample2\":null\r\n}\r\n}"
 ```
 
-{% include note.html
-type='info'
-content='The strings must be escaped and surrounded in quotes.'
-%}
+Note: The strings must be escaped and surrounded in quotes.
 
 ### `generate:suite`
 
@@ -399,11 +386,11 @@ vendor/bin/mftf upgrade:tests /Users/user/magento2/app/code/Magento/Catalog/Test
 
 <!-- LINK DEFINITIONS -->
 
-[configuration]: ../configuration.html
+[configuration]: ../configuration.md
 [Reference]: #reference
 [build]: #buildproject
 [setup]: #setupenv
-[Reporting]: ../reporting.html
+[Reporting]: ../reporting.md
 
 <!-- Abbreviations -->
 

docs/configuration.md

@@ -1,12 +1,6 @@
----
-mftf-release: 2.3.7
-redirect_from: /guides/v2.3/magento-functional-testing-framework/2.3/configuration.html
----
-
 # Configuration
 
-_This topic was updated due to the {{page.mftf-release}} MFTF release._
-{: style="text-align: right"}
+<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
 
 The `*.env` file provides additional configuration for the Magento Functional Testing Framework (MFTF).
 To run the MFTF on your Magento testing instance, specify the basic configuration values.
@@ -26,8 +20,9 @@ Example:
 MAGENTO_BASE_URL=http://magento2.vagrant251
 ```
 
-{: .bs-callout .bs-callout-info }
+<span class=".bs-callout .bs-callout-info">
 If the `MAGENTO_BASE_URL` contains a subdirectory (like `http://magento.test/magento2ce`), specify [`MAGENTO_CLI_COMMAND_PATH`][].
+</span>
 
 ### MAGENTO_BACKEND_NAME
 
@@ -93,9 +88,10 @@ SELENIUM_PROTOCOL=http
 SELENIUM_PATH=/wd/hub
 ```
 
-{:.bs-callout .bs-callout-warning}
+<span class=".bs-callout .bs-callout-warning">
 `SELENIUM_*` values are required if you are running Selenium on an external system.
 If you change the configuration of the external Selenium server, you must update these values.
+</span>
 
 #### SELENIUM_HOST
 
@@ -260,6 +256,6 @@ BROWSER=firefox
 <!-- Link definitions -->
 
 [`MAGENTO_CLI_COMMAND_PATH`]: #magento_cli_command_path
-[generateDate]: test/actions.html#generatedate
-[mftf]: commands/mftf.html
+[generateDate]: test/actions.md#generatedate
+[mftf]: commands/mftf.md
 [timezones]: http://php.net/manual/en/timezones.php

docs/credentials.md

@@ -1,6 +1,3 @@
----
----
-
 # Credentials
 
 When you test functionality that involves external services such as UPS, FedEx, PayPal, or SignifyD, use the MFTF credentials feature to hide sensitive [data][] like integration tokens and API keys.
@@ -69,7 +66,6 @@ carriers_usps_password=Lmgxvrq89uPwECeV
 
 ## Use credentials in a test
 
-<!--{% raw %}-->
 Access the data defined in the `.credentials` file using the [`fillField`][] action with the `userInput` attribute.
 Define the value as a reference to the corresponding key in the credentials file such as `{{_CREDS.my_data_key}}`:
 
@@ -89,13 +85,11 @@ The MFTF dynamically retrieves, encrypts, and decrypts the sensitive data during
 Decrypted credentials do not appear in the console, error logs, or [test reports][].
 The decrypted values are only available in the `.credentials` file.
 
-{: .bs-callout .bs-callout-info }
-The MFTF tests delivered with Magento application do not use credentials and do not cover external services, because of sensitivity of the data.
-
-<!--{% endraw %}-->
+<span class=".bs-callout .bs-callout-info">
+The MFTF tests delivered with Magento application do not use credentials and do not cover external services, because of sensitivity of the data.</span>
 
 <!-- Link definitions -->
-[`fillField`]: test/actions.html#fillfield
-[data]: data.html
-[initial setup]: getting-started.html
-[test reports]: reporting.html
+[`fillField`]: test/actions.md#fillfield
+[data]: data.md
+[initial setup]: getting-started.md
+[test reports]: reporting.md

docs/data.md

@@ -1,21 +1,14 @@
----
-mftf-release: 2.3.0
-redirect_from: /guides/v2.3/magento-functional-testing-framework/2.3/data.html
----
-
 # Input testing data
 
-_This topic was updated due to the {{page.mftf-release}} MFTF release._
-{: style="text-align: right"}
+<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:
 
-{%include_relative img/data-dia.svg%}
+<img src="img/data-dia.svg" />
 
 ## Supply data to test by reference to a data entity
 
-{%raw%}
 Test steps requiring `<data>` input in an action, like filling a field with a string, may reference an attribute from a data entity:
 
 ```xml
@@ -64,28 +57,22 @@ Example of referencing `data` in a test:
 userInput="$createCustomer.email$"
 ```
 
-{%endraw%}
 In this example:
 
 * `createCustomer` is a step key of the corresponding test step that creates an entity.
 * `email` is a data key of the entity.
   The corresponding value will be assigned to `userInput` as a result.
 
-{%
-include note.html
-type="info"
-content='As of MFTF 2.3.6, you no longer need to differentiate between scopes (a test, a hook, or a suite) for persisted data when referencing it in tests.
+Note: As of MFTF 2.3.6, you no longer need to differentiate between scopes (a test, a hook, or a suite) for persisted data when referencing it in tests.
 
 The MFTF now stores the persisted data and attempts to retrieve it using the combination of `stepKey` and the scope of where it has been called.
 The current scope is preferred, then widening to _test > hook > suite_ or _hook > test > suite_.
 
-This emphasizes the practice for the `stepKey` of `createData` to be descriptive and unique, as a duplicated `stepKey` in both a `<test>` and `<before>` prefers the `<test>` data.'
-%}
+This emphasizes the practice for the `stepKey` of `createData` to be descriptive and unique, as a duplicated `stepKey` in both a `<test>` and `<before>` prefers the `<test>` data.
 
 ## Use data returned by test actions
 
-{%raw%}
-A test can also reference data that was returned as a result of [test actions](./test/actions.html#actions-returning-a-variable), like the action `<grabValueFrom selector="someSelector" stepKey="grabStepKey>`.
+A test can also reference data that was returned as a result of [test actions](./test/actions.md#actions-returning-a-variable), like the action `<grabValueFrom selector="someSelector" stepKey="grabStepKey>`.
 
 Further in the test, the data grabbed by the `someSelector` selector can be referenced using the `stepKey` value. In this case, it is `grabStepKey`.
 
@@ -100,7 +87,7 @@ The following example shows the usage of `grabValueFrom` in testing, where the r
 
 The data to operate against can be included as literals in a test. Hard-coded data input can be useful in assertions.
 
-See also [Actions](./test/actions.html).
+See also [Actions](./test/actions.md).
 
 ```xml
 userInput="We'll email you an order confirmation with details and tracking info."
@@ -261,6 +248,4 @@ Attributes|Type|Use|Description
 
 ### item {#item-tag}
 
-`<item>` is an individual piece of data to be passed in as part of the parent `<array>` type.
-
-{%endraw%}
+`<item>` is an individual piece of data to be passed in as part of the parent `<array>` type.

docs/debugging.md

@@ -1,7 +1,4 @@
----
-title: Debugging MFTF Tests
-mftf-release: 2.3.13
----
+# Debugging
 
 Debugging within the Magento Functional Testing Framework is helpful in identifying test bugs by allowing you to pause execution so that you may:
 

docs/extending.md

@@ -1,12 +1,6 @@
----
-mftf-release: 2.3.0
-redirect_from: /guides/v2.3/magento-functional-testing-framework/2.3/extending.html
----
-
 # Extending
 
-_This topic was updated due to the {{page.mftf-release}} MFTF release._
-{: style="text-align: right"}
+<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
 
 There are cases when you need to create many tests that are very similar to each other.
 For example, only one or two parameters (for example, URL) might vary between tests.
@@ -366,7 +360,7 @@ __Use case__: Create an entity named `DivPanelGreen`, which is similar to the `D
 ```
 
 <!-- Link definitions -->
-[test]: ./test.html
-[data]: ./data.html
-[action group]: ./test/action-groups.html
-[actions]: ./test/actions.html
+[test]: ./test.md
+[data]: ./data.md
+[action group]: ./test/action-groups.md
+[actions]: ./test/actions.md