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
These help set the `default` state of the Magento instance. If you wish to change the default state of the application (and have updated your tests sufficiently to account for it), this is the step in which you would do it.
42
42
43
+
If your magento instance has Two-Factor Authentication enabled, see [Configure 2FA][] to configure MFTF tests.
44
+
43
45
## Install allure
44
46
45
47
This will be required to generate the report after your test runs. See [Allure][] for details.
@@ -54,7 +56,7 @@ Generate tests based on what you want to run:
54
56
vendor/bin/mftf generate:tests
55
57
```
56
58
57
-
This will generate all tests and a single manifest file under `dev/tests/acceptance/tests/functional/Magento/FunctionalTest/_generated/testManifest.txt`
59
+
This will generate all tests and a single manifest file under `dev/tests/acceptance/tests/functional/Magento/_generated/testManifest.txt`
58
60
59
61
### Parallel execution
60
62
@@ -64,7 +66,7 @@ To generate all tests for use in parallel nodes:
64
66
vendor/bin/mftf generate:tests --config parallel
65
67
```
66
68
67
-
This will generate a folder under `dev/tests/acceptance/tests/functional/Magento/FunctionalTest/_generated/groups`. This folder contains several `group#.txt` files that can be used later with the `mftf run:manifest` command.
69
+
This will generate a folder under `dev/tests/acceptance/tests/functional/Magento/_generated/groups`. This folder contains several `group#.txt` files that can be used later with the `mftf run:manifest` command.
68
70
69
71
## Delegate and run tests
70
72
@@ -73,21 +75,24 @@ This will generate a folder under `dev/tests/acceptance/tests/functional/Magento
To run MFTF tests in parallel, clone the contents of the current node and duplicate them depending on how many nodes you have.
83
+
You can optimize your pipeline by running tests in parallel across multiple nodes.
84
+
85
+
Tests can be split up into roughly equal running groups using `--config parallel`.
86
+
87
+
You don't want perform installation on each node again and build it. So, to save time, stash pre-made artifacts from earlier steps and un-stash on the nodes.
82
88
83
-
- Clone contents of current node as a baseline.
84
-
- For each `groups/group#.txt` file:
89
+
The groups can be then distributed on each of the nodes and run separately in an isolated environment.
85
90
86
-
-Set a node's contents to the baseline.
87
-
- Run `vendor/bin/mftf run:manifest <current_group.txt>`.
88
-
- Gather artifacts from `dev/tests/acceptance/tests/_output` from current node to master.
91
+
- Stash artifacts from main node and un-stash on current node.
92
+
- Run `vendor/bin/mftf run:manifest <current_group.txt>` on current node.
93
+
- Gather artifacts from `dev/tests/acceptance/tests/_output` from current node to main node.
89
94
90
-
####Rerun options
95
+
### Rerun options
91
96
92
97
In either single or parallel execution, to re-run failed tests simply add the `run:failed` command after executing a manifest:
93
98
@@ -97,12 +102,13 @@ vendor/bin/mftf run:failed
97
102
98
103
### Generate Allure report
99
104
100
-
In the master node, simply generate using your `<path_to_results>` into a desired output path
105
+
In the main node, simply generate using your `<path_to_results>` into a desired output path
0 commit comments