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
Copy file name to clipboardExpand all lines: docs/guides/using-suites.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,14 @@
2
2
3
3
With increasing number of MFTF tests, it's important to have a mechanism to organize and consolidate them for ease-of-use.
4
4
5
-
## What is a suite?
5
+
###What is a suite?
6
6
7
7
Suite is a collection of MFTF tests that are intended to test specific behaviors of Magento. It may contain common initialization and clean up steps specific to the test cases included. It allows you to include, exclude and/or group tests with preconditions and post conditions.
8
8
You can create a suite referencing tests, test groups and modules.
9
9
10
10
### How is a suite defined?
11
11
12
-
Suite must be defined under `<magento 2 root>/dev/tests/acceptance/tests/_suite`as an xml file. The generated tests for each suite are grouped into their own directory under `<magento 2 root>/dev/tests/acceptance/tests/functional/Magento/FunctionalTest/_generated/`
12
+
A suite should be created under `<magento 2 root>/dev/tests/acceptance/tests/_suite`if it has cross-module references. If a suite references only a specific module, it should be created under `<module>/Test/Mftf/Suite`. The generated tests for each suite are grouped into their own directory under `<magento 2 root>/dev/tests/acceptance/tests/functional/Magento/FunctionalTest/_generated/`.
13
13
14
14
### What is the format of a suite?
15
15
@@ -23,7 +23,7 @@ A suite comprises of the below blocks:
0 commit comments