Added 2.2 docs

Author: dshevtsov

best-practices.md

@@ -1,6 +1,6 @@
 ---
-mftf-release: 2.3.0
-redirect_from: /guides/v2.3/magento-functional-testing-framework/2.3/best-practices.html
+mftf-release: 2.2.0
+redirect_from: /guides/v2.2/magento-functional-testing-framework/2.2/best-practices.html
 ---
 
 # Best practices
@@ -16,31 +16,6 @@ Check out our best practices below to ensure you're getting the absolute most ou
  Add additional explanation in comments if needed. 
 2. Provide default values for the arguments that apply to your most common case scenarios.
 
-## `actionGroups` vs `extends`
-
-Use an action group to wraps a set of actions to reuse them multiple times.
-
-Use an [extension] when a test or action group needs to be repeated with the exception of a few steps.
-
-### When to use `extends`
-
-Use `extends` in your new test or action group when at least one of the following conditions is applicable to your case:
-
-1. You want to keep the original test without any modifications.
-2. You want to create a new test that follows the same path as the original test.
-3. You want a new action group that behaves similarly to the existing action group, but you do not want to change the functionality of the original action group.
-
-### When to avoid `extends`
-
-Do not use `extends` in the following conditions:
-1. You want to change the functionality of the test or action group and do not need to run the original version.
-2. You plan to merge the base test or action group.
-
-The following pattern is used when merging with `extends`:
-1. The original test is merged.
-2. The extended test is created from the merged original test.
-3. The extended test is merged.
-
 ## Annotation
 
 1. Use [annotations] in a test. 
@@ -144,19 +119,18 @@ Since the configurable product module could be disabled, this approach is more r
 
 <!-- Link definitions -->
 
+[Action group]: test/action-groups.html
 [`<after>`]: test/actions.html#before-and-after
+[annotations]: test/annotations.html
 [`<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
+[`<wait>`]: test/actions.html#wait
+[`<waitForElement>`]: test/actions.html#waitforelement
+[`<waitForElementVisible>`]: test/actions.html#waitforelementvisible
+[`<waitForLoadingMaskToDisappear>`]: test/actions.html#waitforloadingmasktodisappear

commands/codeception.md

@@ -1,28 +1,32 @@
 ---
-mftf-release: 2.3.0
-redirect_from: /guides/v2.3/magento-functional-testing-framework/2.3/commands/codeception.html
+mftf-release: 2.0.2
+redirect_from: /guides/v2.2/magento-functional-testing-framework/2.2/codeception.html
 ---
 
-# CLI commands: vendor/bin/codecept
+# Codeception commands
 
 _This topic was updated due to the {{page.mftf-release}} MFTF release._
 {: style="text-align: right"}
 
 {:.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 Robo.
 
-To run the Codeception testing framework commands directly, change your directory to `dev/tests/acceptance`.
+See the [list of Robo commands](robo.html). If you'd like to run the Codeception tests directly without using Robo, run:
 
-## Usage examples
+```bash
+vendor/bin/codecept run functional
+```
+
+## Examples
 
-Run all the generated tests:
+Run all tests in `dev/tests/acceptance/tests/functional/Magento/FunctionalTest`:
 
 ```bash
 vendor/bin/codecept run functional
 ```
 
-Run all tests without the `<group value="skip"/>` [annotation](../test/annotations.html):
+Run all tests without the `<group value="skpip"/>` [annotation](../test/annotations.html):
 
 ```bash
 vendor/bin/codecept run functional --skip-group skip
@@ -84,8 +88,3 @@ Full reference:
    --no-ansi             Disable ANSI output.
    --no-interaction (-n) Do not ask any interactive question.
 ```
-
-
-<!-- Link definitions -->
-
-[`mftf` tool]: mftf.html