MAGETWO-60425: [Internal] SITE - Replace FTF images to a separate dir…

…ectory
BarnyShergold · Nov 2, 2016 · 888ee67 · 888ee67
1 parent a78de94
commit 888ee67
Show file tree

Hide file tree

Showing 82 changed files with 69 additions and 69 deletions.
diff --git a/Gemfile b/Gemfile
@@ -3,4 +3,4 @@ source 'https://rubygems.org'
 gem 'github-pages', '83'
 gem 'pygments.rb'
 gem 'jekyll-last-modified-at'
-gem 'wdm', '>= 0.1.0' if Gem.win_platform?
+gem 'wdm', '>= 0.1.0' if Gem.win_platform?
diff --git a/common/images/ftf-reporting-diagram.png → common/images/ftf/ftf-reporting-diagram.png b/common/images/ftf-reporting-diagram.png → common/images/ftf/ftf-reporting-diagram.png
diff --git a/...on/images/mtf_bloch_namepath_ui_onoff.png → ...mages/ftf/mtf_bloch_namepath_ui_onoff.png b/...on/images/mtf_bloch_namepath_ui_onoff.png → ...mages/ftf/mtf_bloch_namepath_ui_onoff.png
diff --git a/common/images/mtf_block_formtab_merge.png → ...on/images/ftf/mtf_block_formtab_merge.png b/common/images/mtf_block_formtab_merge.png → ...on/images/ftf/mtf_block_formtab_merge.png
diff --git a/common/images/mtf_block_login_dir.png → common/images/ftf/mtf_block_login_dir.png b/common/images/mtf_block_login_dir.png → common/images/ftf/mtf_block_login_dir.png
diff --git a/common/images/mtf_block_login_ui.png → common/images/ftf/mtf_block_login_ui.png b/common/images/mtf_block_login_ui.png → common/images/ftf/mtf_block_login_ui.png
diff --git a/common/images/mtf_block_map_form_tab_xml.png → ...images/ftf/mtf_block_map_form_tab_xml.png b/common/images/mtf_block_map_form_tab_xml.png → ...images/ftf/mtf_block_map_form_tab_xml.png
diff --git a/common/images/mtf_block_map_form_xml.png → common/images/ftf/mtf_block_map_form_xml.png b/common/images/mtf_block_map_form_xml.png → common/images/ftf/mtf_block_map_form_xml.png
diff --git a/...on/images/mtf_block_name_path_in_code.png → ...mages/ftf/mtf_block_name_path_in_code.png b/...on/images/mtf_block_name_path_in_code.png → ...mages/ftf/mtf_block_name_path_in_code.png
diff --git a/common/images/mtf_block_name_path_in_ui.png → .../images/ftf/mtf_block_name_path_in_ui.png b/common/images/mtf_block_name_path_in_ui.png → .../images/ftf/mtf_block_name_path_in_ui.png
diff --git a/common/images/mtf_block_tab_composite_ui.png → ...images/ftf/mtf_block_tab_composite_ui.png b/common/images/mtf_block_tab_composite_ui.png → ...images/ftf/mtf_block_tab_composite_ui.png
diff --git a/common/images/mtf_block_tab_struc.png → common/images/ftf/mtf_block_tab_struc.png b/common/images/mtf_block_tab_struc.png → common/images/ftf/mtf_block_tab_struc.png
diff --git a/common/images/mtf_block_tabs_ui.png → common/images/ftf/mtf_block_tabs_ui.png b/common/images/mtf_block_tabs_ui.png → common/images/ftf/mtf_block_tabs_ui.png
diff --git a/common/images/mtf_cache_mngt.png → common/images/ftf/mtf_cache_mngt.png b/common/images/mtf_cache_mngt.png → common/images/ftf/mtf_cache_mngt.png
diff --git a/common/images/mtf_cache_refresh.png → common/images/ftf/mtf_cache_refresh.png b/common/images/mtf_cache_refresh.png → common/images/ftf/mtf_cache_refresh.png
diff --git a/.../images/mtf_constraint_arguments_blue.png → ...ges/ftf/mtf_constraint_arguments_blue.png b/.../images/mtf_constraint_arguments_blue.png → ...ges/ftf/mtf_constraint_arguments_blue.png
diff --git a/.../images/mtf_constraint_arguments_blue.svg → ...ges/ftf/mtf_constraint_arguments_blue.svg b/.../images/mtf_constraint_arguments_blue.svg → ...ges/ftf/mtf_constraint_arguments_blue.svg
diff --git a/...images/mtf_constraint_arguments_green.png → ...es/ftf/mtf_constraint_arguments_green.png b/...images/mtf_constraint_arguments_green.png → ...es/ftf/mtf_constraint_arguments_green.png
diff --git a/...images/mtf_constraint_arguments_green.svg → ...es/ftf/mtf_constraint_arguments_green.svg b/...images/mtf_constraint_arguments_green.svg → ...es/ftf/mtf_constraint_arguments_green.svg
diff --git a/...mages/mtf_constraint_arguments_orange.png → ...s/ftf/mtf_constraint_arguments_orange.png b/...mages/mtf_constraint_arguments_orange.png → ...s/ftf/mtf_constraint_arguments_orange.png
diff --git a/...mages/mtf_constraint_arguments_orange.svg → ...s/ftf/mtf_constraint_arguments_orange.svg b/...mages/mtf_constraint_arguments_orange.svg → ...s/ftf/mtf_constraint_arguments_orange.svg
diff --git a/common/images/mtf_constraint_dir.png → common/images/ftf/mtf_constraint_dir.png b/common/images/mtf_constraint_dir.png → common/images/ftf/mtf_constraint_dir.png
diff --git a/common/images/mtf_constraint_flow.png → common/images/ftf/mtf_constraint_flow.png b/common/images/mtf_constraint_flow.png → common/images/ftf/mtf_constraint_flow.png
diff --git a/common/images/mtf_constraint_variable.png → ...on/images/ftf/mtf_constraint_variable.png b/common/images/mtf_constraint_variable.png → ...on/images/ftf/mtf_constraint_variable.png
diff --git a/common/images/mtf_constraints_variable.ep → ...on/images/ftf/mtf_constraints_variable.ep b/common/images/mtf_constraints_variable.ep → ...on/images/ftf/mtf_constraints_variable.ep
diff --git a/common/images/mtf_dataset_dir.png → common/images/ftf/mtf_dataset_dir.png b/common/images/mtf_dataset_dir.png → common/images/ftf/mtf_dataset_dir.png
diff --git a/...n/images/mtf_ent_fixt_repo_cms_set_ui.png → ...ages/ftf/mtf_ent_fixt_repo_cms_set_ui.png b/...n/images/mtf_ent_fixt_repo_cms_set_ui.png → ...ages/ftf/mtf_ent_fixt_repo_cms_set_ui.png
diff --git a/...ent_fixt_repo_cms_set_ui_frontend-app.png → ...ent_fixt_repo_cms_set_ui_frontend-app.png b/...ent_fixt_repo_cms_set_ui_frontend-app.png → ...ent_fixt_repo_cms_set_ui_frontend-app.png
diff --git a/...f_ent_fixt_repo_cms_set_ui_storefront.png → ...f_ent_fixt_repo_cms_set_ui_storefront.png b/...f_ent_fixt_repo_cms_set_ui_storefront.png → ...f_ent_fixt_repo_cms_set_ui_storefront.png
diff --git a/...ges/mtf_ent_fixt_repo_config_scope-id.png → ...ftf/mtf_ent_fixt_repo_config_scope-id.png b/...ges/mtf_ent_fixt_repo_config_scope-id.png → ...ftf/mtf_ent_fixt_repo_config_scope-id.png
diff --git a/common/images/mtf_features_common_dia.png → ...on/images/ftf/mtf_features_common_dia.png b/common/images/mtf_features_common_dia.png → ...on/images/ftf/mtf_features_common_dia.png
diff --git a/...mages/mtf_features_parallel_multi_dia.png → ...s/ftf/mtf_features_parallel_multi_dia.png b/...mages/mtf_features_parallel_multi_dia.png → ...s/ftf/mtf_features_parallel_multi_dia.png
diff --git a/.../images/mtf_features_parallel_one_dia.png → ...ges/ftf/mtf_features_parallel_one_dia.png b/.../images/mtf_features_parallel_one_dia.png → ...ges/ftf/mtf_features_parallel_one_dia.png
diff --git a/common/images/mtf_fixture_xml_pic.png → common/images/ftf/mtf_fixture_xml_pic.png b/common/images/mtf_fixture_xml_pic.png → common/images/ftf/mtf_fixture_xml_pic.png
diff --git a/common/images/mtf_layout_update.jpg → common/images/ftf/mtf_layout_update.jpg b/common/images/mtf_layout_update.jpg → common/images/ftf/mtf_layout_update.jpg
diff --git a/common/images/mtf_modularity_dirs.png → common/images/ftf/mtf_modularity_dirs.png b/common/images/mtf_modularity_dirs.png → common/images/ftf/mtf_modularity_dirs.png
diff --git a/common/images/mtf_qstart_mag_secur.png → common/images/ftf/mtf_qstart_mag_secur.png b/common/images/mtf_qstart_mag_secur.png → common/images/ftf/mtf_qstart_mag_secur.png
diff --git a/common/images/mtf_qstart_mag_secur_20.png → ...on/images/ftf/mtf_qstart_mag_secur_20.png b/common/images/mtf_qstart_mag_secur_20.png → ...on/images/ftf/mtf_qstart_mag_secur_20.png
diff --git a/common/images/mtf_qstart_mag_wysiwyg.png → common/images/ftf/mtf_qstart_mag_wysiwyg.png b/common/images/mtf_qstart_mag_wysiwyg.png → common/images/ftf/mtf_qstart_mag_wysiwyg.png
diff --git a/common/images/mtf_repo_config_ex.png → common/images/ftf/mtf_repo_config_ex.png b/common/images/mtf_repo_config_ex.png → common/images/ftf/mtf_repo_config_ex.png
diff --git a/common/images/mtf_repo_merge_ex.png → common/images/ftf/mtf_repo_merge_ex.png b/common/images/mtf_repo_merge_ex.png → common/images/ftf/mtf_repo_merge_ex.png
diff --git a/...tf_repository_layout-allpages_w_dropd.png → ...tf_repository_layout-allpages_w_dropd.png b/...tf_repository_layout-allpages_w_dropd.png → ...tf_repository_layout-allpages_w_dropd.png
diff --git a/...tory_layout-for-cms-page-link_w_dropd.png → ...tory_layout-for-cms-page-link_w_dropd.png b/...tory_layout-for-cms-page-link_w_dropd.png → ...tory_layout-for-cms-page-link_w_dropd.png
diff --git a/..._repository_layout-oncategory_w_dropd.png → ..._repository_layout-oncategory_w_dropd.png b/..._repository_layout-oncategory_w_dropd.png → ..._repository_layout-oncategory_w_dropd.png
diff --git a/common/images/mtf_test_case_flow.png → common/images/ftf/mtf_test_case_flow.png b/common/images/mtf_test_case_flow.png → common/images/ftf/mtf_test_case_flow.png
diff --git a/common/images/mtf_test_case_flow.pub → common/images/ftf/mtf_test_case_flow.pub b/common/images/mtf_test_case_flow.pub → common/images/ftf/mtf_test_case_flow.pub
diff --git a/common/images/mtf_tut_fixt.png → common/images/ftf/mtf_tut_fixt.png b/common/images/mtf_tut_fixt.png → common/images/ftf/mtf_tut_fixt.png
diff --git a/common/images/mtf_tutor_dataset.png → common/images/ftf/mtf_tutor_dataset.png b/common/images/mtf_tutor_dataset.png → common/images/ftf/mtf_tutor_dataset.png
diff --git a/common/images/mtf_tutorial_block_mapping.png → ...images/ftf/mtf_tutorial_block_mapping.png b/common/images/mtf_tutorial_block_mapping.png → ...images/ftf/mtf_tutorial_block_mapping.png
diff --git a/common/images/mtf_tutorial_block_struct.png → .../images/ftf/mtf_tutorial_block_struct.png b/common/images/mtf_tutorial_block_struct.png → .../images/ftf/mtf_tutorial_block_struct.png
diff --git a/...images/mtf_tutorial_block_struct_test.png → ...es/ftf/mtf_tutorial_block_struct_test.png b/...images/mtf_tutorial_block_struct_test.png → ...es/ftf/mtf_tutorial_block_struct_test.png
diff --git a/...on/images/mtf_tutorial_constraint_dir.png → ...mages/ftf/mtf_tutorial_constraint_dir.png b/...on/images/mtf_tutorial_constraint_dir.png → ...mages/ftf/mtf_tutorial_constraint_dir.png
diff --git a/common/images/mtf_tutorial_datasource.png → ...on/images/ftf/mtf_tutorial_datasource.png b/common/images/mtf_tutorial_datasource.png → ...on/images/ftf/mtf_tutorial_datasource.png
diff --git a/common/images/mtf_tutorial_new_syn_ui.png → ...on/images/ftf/mtf_tutorial_new_syn_ui.png b/common/images/mtf_tutorial_new_syn_ui.png → ...on/images/ftf/mtf_tutorial_new_syn_ui.png
diff --git a/.../images/mtf_tutorial_page_new_synonym.png → ...ges/ftf/mtf_tutorial_page_new_synonym.png b/.../images/mtf_tutorial_page_new_synonym.png → ...ges/ftf/mtf_tutorial_page_new_synonym.png
diff --git a/common/images/mtf_tutorial_pages.png → common/images/ftf/mtf_tutorial_pages.png b/common/images/mtf_tutorial_pages.png → common/images/ftf/mtf_tutorial_pages.png
diff --git a/common/images/mtf_tutorial_pages_php.png → common/images/ftf/mtf_tutorial_pages_php.png b/common/images/mtf_tutorial_pages_php.png → common/images/ftf/mtf_tutorial_pages_php.png
diff --git a/...n/images/mtf_tutorial_storeIds-widget.png → ...ages/ftf/mtf_tutorial_storeIds-widget.png b/...n/images/mtf_tutorial_storeIds-widget.png → ...ages/ftf/mtf_tutorial_storeIds-widget.png
diff --git a/...n/images/mtf_tutorial_success_message.png → ...ages/ftf/mtf_tutorial_success_message.png b/...n/images/mtf_tutorial_success_message.png → ...ages/ftf/mtf_tutorial_success_message.png
diff --git a/...images/mtf_tutorial_testcase_location.png → ...es/ftf/mtf_tutorial_testcase_location.png b/...images/mtf_tutorial_testcase_location.png → ...es/ftf/mtf_tutorial_testcase_location.png
diff --git a/common/images/mtf_typ_element_brows.png → common/images/ftf/mtf_typ_element_brows.png b/common/images/mtf_typ_element_brows.png → common/images/ftf/mtf_typ_element_brows.png
diff --git a/common/images/mtf_typ_element_brows.pub → common/images/ftf/mtf_typ_element_brows.pub b/common/images/mtf_typ_element_brows.pub → common/images/ftf/mtf_typ_element_brows.pub
diff --git a/common/images/mtf_typ_element_map_gui.png → ...on/images/ftf/mtf_typ_element_map_gui.png b/common/images/mtf_typ_element_map_gui.png → ...on/images/ftf/mtf_typ_element_map_gui.png
diff --git a/common/images/mtf_typ_element_map_gui.pub → ...on/images/ftf/mtf_typ_element_map_gui.pub b/common/images/mtf_typ_element_map_gui.pub → ...on/images/ftf/mtf_typ_element_map_gui.pub
diff --git a/common/images/mtf_widget_handler_tree.png → ...on/images/ftf/mtf_widget_handler_tree.png b/common/images/mtf_widget_handler_tree.png → ...on/images/ftf/mtf_widget_handler_tree.png
diff --git a/guides/v2.0/mtf/create_test/create_new_test.md b/guides/v2.0/mtf/create_test/create_new_test.md
@@ -103,7 +103,7 @@ All slashes must be escaped with `\\`.
 
 As a result of previous commands, a brand new fixture can be found in the `<magento2_root_dir>/dev/tests/functional/tests/app/Magento/Search/Test/Fixture` directory.
 
-![A new Synonym fixture]({{site.baseurl}}common/images/mtf_tut_fixt.png)
+![A new Synonym fixture]({{site.baseurl}}common/images/ftf/mtf_tut_fixt.png)
 
 The following is a code of the new Synonym fixture.
 
@@ -129,15 +129,15 @@ The following is a code of the new Synonym fixture.
 
 If we open a New Synonym Group page in a browser
 
-![New Synonym Group page]({{ site.baseurl }}common/images/mtf_tutorial_new_syn_ui.png)
+![New Synonym Group page]({{ site.baseurl }}common/images/ftf/mtf_tutorial_new_syn_ui.png)
 
 we see that `store_id` and `website_id` are combined in the "Scope" fields. To set `store_id` and `website_id`, we have to perform some more logic than just entering the data. That's why we should use a [data source][].
 
 The same field is present in Magento_Widget module. It means that data source has been already written and we can reuse it.
 
 Let's check the functional tests for the Magento_Widget module.
 
-![ScopeID data source alternative from Magento_Widget]({{ site.baseurl }}common/images/mtf_tutorial_storeIds-widget.png)
+![ScopeID data source alternative from Magento_Widget]({{ site.baseurl }}common/images/ftf/mtf_tutorial_storeIds-widget.png)
 
 It contains a `StoreIds.php` data source, that is similar to what we need. It has the following code:
 
@@ -272,7 +272,7 @@ This data source:
 
 We should save it as `<magento2_root_dir>/dev/tests/functional/tests/app/Magento/Search/Test/Fixture/Synonym/ScopeId.php`.
 
-![Synonym ScopeID data source location]({{site.baseurl}}common/images/mtf_tutorial_datasource.png)
+![Synonym ScopeID data source location]({{site.baseurl}}common/images/ftf/mtf_tutorial_datasource.png)
 
 Now we should change the fixture. Instead of `store_id` and `website_id`, we must use `scope_id` with the `Magento\Search\Test\Fixture\Synonym\ScopeId` data source class.
 
@@ -373,7 +373,7 @@ Now we can create a [test case][].
 From the [test case topic][] we know about the structure, location and name of the test case.
 In this example it is named `CreateSynonymEntityTest.php` and stored in `<magento2_root_dir>/dev/tests/functional/tests/app/Magento/Search/Test/TestCase`.
 
- ![A test case location]({{site.baseurl}}common/images/mtf_tutorial_testcase_location.png)
+ ![A test case location]({{site.baseurl}}common/images/ftf/mtf_tutorial_testcase_location.png)
 
 As a result of [manual testing][] we know that we must work with a Search Synonym Index page and a New Synonym Group page during the test flow. We can code the initialization of these pages in the test using an `__inject()` method of the `Magento\Mtf\TestCase\Injectable` class. The pages will be created in [Step 5][]. Also, we will use the fixture from the [Step 2][].
 
@@ -444,7 +444,7 @@ class CreateSynonymEntityTest extends Injectable
 
 Now we can add a [data set][] with variations that cover cases in the [test description][]: `<magento2_root_dir>/dev/tests/functional/tests/app/Magento/Search/Test/TestCase/CreateSynonymEntityTest.xml`
 
-![Created data set]({{site.baseurl}}common/images/mtf_tutor_dataset.png)
+![Created data set]({{site.baseurl}}common/images/ftf/mtf_tutor_dataset.png)
 
 The following code contains a data set, but doesn't have data yet:
 
@@ -534,13 +534,13 @@ In [Step 3][], we added two [pages][] to the test case class. Because both pages
 
 {% endhighlight %}
 
-![Created pages]({{site.baseurl}}common/images/mtf_tutorial_pages.png)
+![Created pages]({{site.baseurl}}common/images/ftf/mtf_tutorial_pages.png)
 
 To generate PHP classes for these [pages][] enter and run in your terminal
 
     php <magento2_root_dir>/dev/tests/functional/utils/generate.php
 
-![PHP classes of pages]({{site.baseurl}}common/images/mtf_tutorial_pages_php.png)
+![PHP classes of pages]({{site.baseurl}}common/images/ftf/mtf_tutorial_pages_php.png)
 
 In the next step we will create [blocks][] that implements logic in these pages.
 
@@ -591,15 +591,15 @@ Now you can run `generate.php` as we did before to re-generate page classes.
 
 We need to enter data from a data set into the form fields.
 
-![New Synonym Group page]({{site.baseurl}}common/images/mtf_tutorial_page_new_synonym.png)
+![New Synonym Group page]({{site.baseurl}}common/images/ftf/mtf_tutorial_page_new_synonym.png)
 
 The `Block` directory in the Magento_Search module (in the Magento code) contains the `Adminhtml/Synonyms/Edit` directories, as shown below:
 
-![Block structure in a code base]({{site.baseurl}}common/images/mtf_tutorial_block_struct.png) 
+![Block structure in a code base]({{site.baseurl}}common/images/ftf/mtf_tutorial_block_struct.png) 
 
 The `Search/Test` directory in functional tests should be constructed in a similar manner:
 
-![Block structure in a functional test]({{site.baseurl}}common/images/mtf_tutorial_block_struct_test.png) 
+![Block structure in a functional test]({{site.baseurl}}common/images/ftf/mtf_tutorial_block_struct_test.png) 
 
 We need a `fill()` method from the [`\Magento\Mtf\Block\Form`][] class and a mapping file.
 
@@ -644,7 +644,7 @@ class SynonymsForm extends Form
 
 Now we have the following structure:
 
-![Form mapping block]({{site.baseurl}}common/images/mtf_tutorial_block_mapping.png)
+![Form mapping block]({{site.baseurl}}common/images/ftf/mtf_tutorial_block_mapping.png)
 
 
 Then we should add the block class to the `SynonymsNew.xml` page object. To identify a form block on the HTML page, use an `id='page:main-container'` css selector.
@@ -905,7 +905,7 @@ You can run the test using your IDE or the CLI. The Selenium Server must be [up
 
 The last item in the test description says that the test must check that a success message is displayed after the test flow completes.
 
-![Message about the successful save]({{site.baseurl}}common/images/mtf_tutorial_success_message.png)
+![Message about the successful save]({{site.baseurl}}common/images/ftf/mtf_tutorial_success_message.png)
 
 To cover this, we should create the test assertion ([constraint][]) and add the full class name to a variation of the data set. 
 
@@ -964,7 +964,7 @@ class AssertCustomerSuccessSaveMessage extends AbstractConstraint
 
 By making a simple change, we can create a constraint class that is needed `\Magento\Search\Test\Constraint\AssertSynonymSuccessSaveMessage`
 
-![A constraint location]({{site.baseurl}}common/images/mtf_tutorial_constraint_dir.png)
+![A constraint location]({{site.baseurl}}common/images/ftf/mtf_tutorial_constraint_dir.png)
 
 with the following code:
 

diff --git a/guides/v2.0/mtf/features/modularity.md b/guides/v2.0/mtf/features/modularity.md
@@ -12,7 +12,7 @@ github_link: mtf/features/modularity.md
 
 The Functional Testing Framework (FTF) enables you to follow the principle of modularity as Magento does. Functional tests for each module are collected in separate directory with the name of corresponding module.
 
-![Functional tests modules image]({{site.baseurl}}common/images/mtf_modularity_dirs.png)
+![Functional tests modules image]({{site.baseurl}}common/images/ftf/mtf_modularity_dirs.png)
 
 Modularity gives the following advantages:
 

diff --git a/guides/v2.0/mtf/features/parallel_execution.md b/guides/v2.0/mtf/features/parallel_execution.md
@@ -26,15 +26,15 @@ A general mechanism is:
 
 Comparatively to the common testing flow
 
-![Common flow image]({{site.baseurl}}common/images/mtf_features_common_dia.png)
+![Common flow image]({{site.baseurl}}common/images/ftf/mtf_features_common_dia.png)
 
 you can run a test suite using parallel execution flow with one Magento instance
 
-![Parallel execution flow with one instance image]({{site.baseurl}}common/images/mtf_features_parallel_one_dia.png)
+![Parallel execution flow with one instance image]({{site.baseurl}}common/images/ftf/mtf_features_parallel_one_dia.png)
 
 or run a test suite using parallel execution flow with multiple Magento instances.
 
-![Common flow and Parallel execution flow image]({{site.baseurl}}common/images/mtf_features_parallel_multi_dia.png)
+![Common flow and Parallel execution flow image]({{site.baseurl}}common/images/ftf/mtf_features_parallel_multi_dia.png)
 
 ## Set up parallel execution
 

diff --git a/guides/v2.0/mtf/features/reporting.md b/guides/v2.0/mtf/features/reporting.md
@@ -19,7 +19,7 @@ The Functional Testing Framework (FTF) provides a reporting tool, which logs fai
 
 The following image demonstrates example of a general flow.  
 
-<a href="{{site.baseurl}}common/images/ftf-reporting-diagram.png" alt="Reporting mechanism diagram" target="_blank"><img src="{{site.baseurl}}common/images/ftf-reporting-diagram.png" /></a>
+<a href="{{site.baseurl}}common/images/ftf/ftf-reporting-diagram.png" alt="Reporting mechanism diagram" target="_blank"><img src="{{site.baseurl}}common/images/ftf/ftf-reporting-diagram.png" /></a>
 
 The event manager is a core component which:
 

diff --git a/guides/v2.0/mtf/mtf_entities/mtf_block.md b/guides/v2.0/mtf/mtf_entities/mtf_block.md
@@ -58,11 +58,11 @@ To enable this feature follow:
 1. Set **Add Block Name to Hints** to **Yes**
 1. **Save Config**
 
-![]({{site.baseurl}}common/images/mtf_bloch_namepath_ui_onoff.png)
+![]({{site.baseurl}}common/images/ftf/mtf_bloch_namepath_ui_onoff.png)
 
 Now each UI block has hint about its name and path. Also, you can see the path to a PHTML template, where you can find a path to the Magento block, if you cannot find it in the hint.
 
-<a href="{{ site.baseurl }}common/images/mtf_block_name_path_in_ui.png"><img src="{{ site.baseurl }}common/images/mtf_block_name_path_in_ui.png" /></a>
+<a href="{{ site.baseurl }}common/images/ftf/mtf_block_name_path_in_ui.png"><img src="{{ site.baseurl }}common/images/ftf/mtf_block_name_path_in_ui.png" /></a>
 
 <div class="bs-callout bs-callout-tip">
   <p>If the name and path cover partially each other, hover the mouse pointer over the name or the path (whatever you need) with mouse pointer to see the full phrase.</p>
@@ -111,7 +111,7 @@ protected function _toHtml()
 
 Now you can inspect any element in a browser, and find which block contains it.
 
-<a href="{{ site.baseurl }}common/images/mtf_block_name_path_in_code.png"><img src="{{ site.baseurl }}common/images/mtf_block_name_path_in_code.png" /></a>
+<a href="{{ site.baseurl }}common/images/ftf/mtf_block_name_path_in_code.png"><img src="{{ site.baseurl }}common/images/ftf/mtf_block_name_path_in_code.png" /></a>
 
 ### Block class {#mtf_block_class}
 
@@ -202,11 +202,11 @@ A mapping file is an XML file which has the same name and path as the block does
 
 Let's see the [Customer Login]({{site.mage2000url}}app/code/Magento/Customer/Block/Form/Login.php) block. The block has two input fields: `email` and `password`.
 
-<a href="{{site.baseurl}}common/images/mtf_block_login_ui.png"><img src="{{site.baseurl}}common/images/mtf_block_login_ui.png" /></a>
+<a href="{{site.baseurl}}common/images/ftf/mtf_block_login_ui.png"><img src="{{site.baseurl}}common/images/ftf/mtf_block_login_ui.png" /></a>
 
 The mapping file for the block is stored in `<magento2_root_dir>/dev/tests/functional/tests/app/Magento/Customer/Test/Block/Form/Login.xml`, along with the block.
 
-<img src="{{site.baseurl}}common/images/mtf_block_login_dir.png" />
+<img src="{{site.baseurl}}common/images/ftf/mtf_block_login_dir.png" />
 
 The mapping file defines the fields from the form.
 
@@ -247,7 +247,7 @@ All nodes are optional. Default value is assigned automatically if a node (`sele
 
 The general structure of the form mapping file:
 
-<img src="{{site.baseurl}}common/images/mtf_block_map_form_xml.png" />
+<img src="{{site.baseurl}}common/images/ftf/mtf_block_map_form_xml.png" />
 
 ### Form tab mapping {#mtf_block_map_form_tab}
 
@@ -256,11 +256,11 @@ To get the block class with form tab mapping, extend your class from <a href="{{
 
 For example, let's see tabs for the Magento Widget: **Settings**, **Storefront properties**, **Frontend App Options**, **Layout Updates** .
 
-<img src="{{site.baseurl}}common/images/mtf_block_tabs_ui.png" />
+<img src="{{site.baseurl}}common/images/ftf/mtf_block_tabs_ui.png" />
 
 Four tabs are mapped in the `<magento2_root_dir>/dev/tests/functional/tests/app/Magento/Widget/Test/Block/Adminhtml/Widget/Instance/Edit/WidgetForm.xml` file, which is stored along with the block class. 
 
-<img src="{{site.baseurl}}common/images/mtf_block_tab_struc.png" />
+<img src="{{site.baseurl}}common/images/ftf/mtf_block_tab_struc.png" />
 
 The file contains the following mapping:
 
@@ -344,11 +344,11 @@ In the mapping file:
 
 On the UI:
 
-![Example of `composite` field]({{site.baseurl}}common/images/mtf_block_tab_composite_ui.png)
+![Example of `composite` field]({{site.baseurl}}common/images/ftf/mtf_block_tab_composite_ui.png)
 
 The general structure of the form tab mapping file:
 
-<img src="{{site.baseurl}}common/images/mtf_block_map_form_tab_xml.png" />
+<img src="{{site.baseurl}}common/images/ftf/mtf_block_map_form_tab_xml.png" />
 
 ### Merging form tab mapping files {#mtf_block_map_form_tab_merge}
 
@@ -358,7 +358,7 @@ The form tab mapping files that have the same name and path inside different mod
 
 Form tab mapping files in the following example will be merged automatically:
 
-<img src="{{site.baseurl}}common/images/mtf_block_formtab_merge.png" />
+<img src="{{site.baseurl}}common/images/ftf/mtf_block_formtab_merge.png" />
 
 ## Renders {#mtf_block_render}
 

diff --git a/guides/v2.0/mtf/mtf_entities/mtf_constraint.md b/guides/v2.0/mtf/mtf_entities/mtf_constraint.md
@@ -19,15 +19,15 @@ github_link: mtf/mtf_entities/mtf_constraint.md
 The Functional Testing Framework (FTF) constraint performs assertions after a test flow. A test flow is a set of test steps without assertions.
 Each constraint name must be globally unique in Magento application and must be placed in the module to which it belongs. Constraints run automatically after test flow has finished.
 
-![Constraints and test flow]({{site.baseurl}}common/images/mtf_constraint_flow.png)
+![Constraints and test flow]({{site.baseurl}}common/images/ftf/mtf_constraint_flow.png)
 
 ## Constraint structure {#mtf_constraint_structure}
 
 ### `Constraint` directory {#mtf_constraint_directory}
 
 A module in functional tests (`<magento2_root_dir>/dev/tests/app/Magento/`) stores constraints in the `Constraint` directory. The following image shows the `Constraint` directory of the Magento_Widget module.
 
-![]({{site.baseurl}}common/images/mtf_constraint_dir.png)
+![]({{site.baseurl}}common/images/ftf/mtf_constraint_dir.png)
 
 ### Constraint class {#mtf_constraint_assert}
 
@@ -56,15 +56,15 @@ An object that is not defined in the data set or isn't returned from the test ca
 
 Let's see the following images for the `CreateSimpleProductEntityTest` test and the `AssertProductPricesOnCategoryPage` constraint. Data set from the diagrams contains three variables with data: `product`, `category` and `price`.
 
-<img src="{{ site.baseurl }}common/images/mtf_constraint_arguments_green.png" width="800" />
+<img src="{{ site.baseurl }}common/images/ftf/mtf_constraint_arguments_green.png" width="800" />
 
 <span style="color: #21610B; font-weight:bold">Green arrows</span> show that `product` value is transferred to the test and the constraint.
 
-<img src="{{ site.baseurl }}common/images/mtf_constraint_arguments_orange.png" width="800" />
+<img src="{{ site.baseurl }}common/images/ftf/mtf_constraint_arguments_orange.png" width="800" />
 
 <span style="color: #FF8000; font-weight:bold">Orange arrows</span> show that `category` variable is transferred to the test directly, overwritten by `testCreate()` method and only then transferred to constraint.
 
-<img src="{{ site.baseurl }}common/images/mtf_constraint_arguments_blue.png" width="800"/>
+<img src="{{ site.baseurl }}common/images/ftf/mtf_constraint_arguments_blue.png" width="800"/>
 
 <span style="color: #0000FF; font-weight:bold">Blue arrow</span> shows that `price` value is transferred to the constraint only.
 

diff --git a/guides/v2.0/mtf/mtf_entities/mtf_dataset.md b/guides/v2.0/mtf/mtf_entities/mtf_dataset.md
@@ -103,7 +103,7 @@ A data set should be placed in the same directory with a corresponding test case
 
 Let's see an example for `CreateSimpleProductEntityTest`. A data set and its corresponding [test case][] must be placed in the `<magento2_root_dir>/dev/tests/functional/tests/app/Magento/Catalog/Test/TestCase/Product` directory.
 
-<a href="{{ site.baseurl }}common/images/mtf_dataset_dir.png"><img src="{{ site.baseurl }}common/images/mtf_dataset_dir.png"/></a>
+<a href="{{ site.baseurl }}common/images/ftf/mtf_dataset_dir.png"><img src="{{ site.baseurl }}common/images/ftf/mtf_dataset_dir.png"/></a>
 
 The `CreateSimpleProductEntityTest.xml` data set contains: