You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 19, 2019. It is now read-only.
Merge pull request #1560 from magento-pangolin/MQE-420
[Pangolin] Deliver changes after MFTF training feedback
- MQE-369: [Data Input] Non Web Api Data Persistence.
- MQE-378: Create API metadata for Coupon Code
- MQE-309: [Customizability] Update nested API dependency schema and execution
- MQE-365: Template Files
- MQE-411: Fixed template and coupon meta data files.
- MQE-402: Workshop Feedback
- MQE-352: Review and Update SampleCest.xml for added functionality
- MQE-419: README.MD should not reference the magento-pangolin org
- MQE-424: Fix static code issues in MFTF tests and MFTF
Copy file name to clipboardExpand all lines: dev/tests/acceptance/README.md
+58-34Lines changed: 58 additions & 34 deletions
Original file line number
Diff line number
Diff line change
@@ -8,18 +8,20 @@
8
8
----
9
9
10
10
# Prerequisites
11
-
***IMPORTANT**: Configure your Magento Store for [Automated Testing](http://devdocs.magento.com/guides/v2.0/mtf/mtf_quickstart/mtf_quickstart_magento.html)
11
+
***IMPORTANT**
12
+
* You will need to have a running instance of Magento that you can access.
13
+
* You will need to configure your instance of Magento for [Automated Testing](http://devdocs.magento.com/guides/v2.0/mtf/mtf_quickstart/mtf_quickstart_magento.html).
* We recommend using [PHPStorm 2017](https://www.jetbrains.com/phpstorm/) for your IDE. They recently added support for [Codeception Test execution](https://blog.jetbrains.com/phpstorm/2017/03/codeception-support-comes-to-phpstorm-2017-1/) which is helpful when debugging.
22
-
* We also recommend updating your [$PATH to include](https://stackoverflow.com/questions/7703041/editing-path-variable-on-mac)`./vendor/bin` so you can easily execute the necessary `robo` and `codecept` commands instead of `./vendor/bin/robo` or `./vendor/bin/codecept`.
24
+
* We also recommend updating your [$PATH to include](https://stackoverflow.com/questions/7703041/editing-path-variable-on-mac)`./vendor/bin` so you can easily execute the necessary `robo` and `codecept` commands instead of using `./vendor/bin/robo` or `./vendor/bin/codecept`.
23
25
24
26
----
25
27
@@ -28,19 +30,29 @@ Due to the current setup of the Framework you will need to do the following:
28
30
29
31
*`mkdir [DIRECTORY_NAME]`
30
32
*`cd [DIRECTORY_NAME]`
31
-
* Pull down - [EE](https://github.com/magento-pangolin/magento2ee)
32
-
* Pull down - [CE](https://github.com/magento-pangolin/magento2ce)
33
+
* Pull down - [EE](https://github.com/magento/magento2ee)
34
+
* Pull down - [CE](https://github.com/magento/magento2ce)
* Generate a `github-oauth` token: [Instructions](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/#creating-a-token)
37
+
*`cd ..`
38
+
* Generate a `github-oauth` token:
39
+
*[How to setup an auth.json file for the Composer?](https://mage2.pro/t/topic/743)
40
+
*[Creating a personal access token for the command line.](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/#creating-a-token)
* Replace `<personal access token>` with the token you generated in GitHub.
39
52
* Save your work.
40
-
*`cd ../magento2ce`
41
-
*`cd dev/tests/acceptance`
53
+
* `cd magento2ce/dev/tests/acceptance`
42
54
* `composer install`
43
-
***PLEASE IGNORE THE "Installation" SECTION THAT FOLLOWS, START WITH THE "Building The Framework" SECTION INSTEAD.**
55
+
* **PLEASE IGNORE THE "Installation" SECTION THAT FOLLOWS, START WITH THE "Building The Framework" SECTION INSTEAD.**
44
56
45
57
----
46
58
@@ -116,7 +128,7 @@ To determine which version of the Allure command you need to use please run `all
116
128
----
117
129
118
130
# Building The Framework
119
-
After installing the dependencies you will want to build the Codeception project in the [Magento 2 Functional Testing Framework](https://github.com/magento-pangolin/magento2-functional-testing-framework), which is a dependency of the CE or EE Tests repo. Run `./vendor/bin/robo build:project` to complete this task.
131
+
After installing the dependencies you will want to build the Codeception project in the [Magento 2 Functional Testing Framework](https://github.com/magento/magento2-functional-testing-framework), which is a dependency of the CE or EE Tests repo. Run the following to complete this task:
120
132
121
133
`./vendor/bin/robo build:project`
122
134
@@ -127,9 +139,15 @@ Before you can generate or run the Tests you will need to edit the Configuration
127
139
128
140
In the `.env` file you will find key pieces of information that are unique to your local Magento setup that will need to be edited before you can generate tests:
* Allure `@env error` - Allure recently changed their Codeception Adapter that breaks Codeception when tests include the `@env` tag. A workaround for this error is to revert the changes they made to a function.
226
-
* Locate the `AllureAdapter.php` file here: `vendor/allure-framework/allure-codeception/src/Yandex/Allure/Adapter/AllureAdapter.php`
227
-
* Edit the `_initialize()` function found on line 77 and replace it with the following:
228
-
```
229
-
public function _initialize(array $ignoredAnnotations = [])
* Allure `@env error` - Allure recently changed their Codeception Adapter that breaks Codeception when tests include the `@env` tag. There are 2 workarounds for this issue currently.
244
+
1. You can edit the `composer.json` and point the Allure-Codeception Adapter to a previous commit:
0 commit comments