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
By default, Allure generates reports in the `allure-report/` at the current directory.
304
304
For example, if you run the command without `-o` flag while you are in the `magento2/` directory, Allure will generate a report at the `magento2/allure-report/` directory.
There is no need to use sequential variables like `{{var1}}`, `{{var2}}`. Parameterized replacement reads variables and maps them to the test call of the element sequentially from left to right, meaning you can use a selector like `#element .{{categoryId}} .{{productId}}`."
Copy file name to clipboardExpand all lines: docs/test/actions.md
+2-4
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,5 @@
1
1
# Test actions
2
2
3
-
4
3
Actions in the MFTF allow you to automate different scenarios of Magento user's actions.
5
4
They are mostly XML implementations of [Codeception actions](http://codeception.com/docs/modules/WebDriver#Actions).
6
5
Some actions drive browser elements, while others use REST APIs.
@@ -153,7 +152,6 @@ The only difference is that different data is assigned to the attributes, which
153
152
<!-- {% endraw %} -->
154
153
155
154
Here, [`<click>`](#click) performs a click on a button that can be found by the selector that is stored in the `signInAccountButton` of the `StorefrontCustomerSignInFormSection`.
156
-
See the `StorefrontCustomerSignInPage.xml` file code in [step 2](#section-code).
157
155
158
156
## Actions returning a variable
159
157
@@ -1349,7 +1347,7 @@ Note that the makeScreenshot action does not automatically add the screenshot to
Copy file name to clipboardExpand all lines: docs/test/annotations.md
+5-3
Original file line number
Diff line number
Diff line change
@@ -77,11 +77,13 @@ The `<group>` element is an implementation of a [`@group`] Codeception tag.
77
77
Any test can be a part of multiple groups.
78
78
The purpose of grouping is to create a set of test for a functionality or purpose, such as all cart tests or all slow tests and run them together locally.
Copy file name to clipboardExpand all lines: docs/tips-tricks.md
+9-9
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ In the bad example we see two parameters being passed into the selector with lit
13
13
14
14
**Why?** The next person maintaining the test or extending it may not be able to understand what the parameters are referencing.
15
15
16
-
<spanstype="color:green">
16
+
<spanstyle="color:green">
17
17
Good
18
18
</span>
19
19
@@ -54,7 +54,7 @@ In the bad example, we perform some heavy UI steps first.
54
54
55
55
**Why?** If something goes wrong there, then the critical `magentoCLI` commands may not get a chance to run, leaving Magento configured incorrectly for any upcoming tests.
56
56
57
-
<spanstype="color:green">
57
+
<spanstyle="color:green">
58
58
Good:
59
59
</span>
60
60
@@ -108,7 +108,7 @@ And for `seeElement` it will output something like this:
108
108
There is a subtle distinction: The first is a failure but it is the desired result: a 'positive failure'.
109
109
The second is a proper result of the action.
110
110
111
-
<spanstype="color:green">
111
+
<spanstyle="color:green">
112
112
Good:
113
113
</span>
114
114
@@ -128,7 +128,7 @@ Bad:
128
128
129
129
Whenever possible, specify a `defaultValue` for action group arguments.
130
130
131
-
<spanstype="color:green">
131
+
<spanstyle="color:green">
132
132
GOOD:
133
133
</span>
134
134
@@ -176,7 +176,7 @@ Build your tests using action groups, even if an action group contains a single
176
176
Extending a single action group will update all tests that use this group.
177
177
This improves maintainability as multiple instances of a failure can be fixed with a single action group update.
178
178
179
-
<spanstype="color:green">
179
+
<spanstyle="color:green">
180
180
GOOD:
181
181
</span>
182
182
@@ -234,7 +234,7 @@ Do not use numbers to make a `stepKey` unique.
234
234
235
235
**Why?** This helps with readability and clarity.
236
236
237
-
<spanstype="color:green">
237
+
<spanstyle="color:green">
238
238
GOOD:
239
239
</span>
240
240
@@ -308,7 +308,7 @@ Example:
308
308
</div>
309
309
```
310
310
311
-
<spanstype="color:green">
311
+
<spanstyle="color:green">
312
312
GOOD:
313
313
</span>
314
314
@@ -358,7 +358,7 @@ BAD:
358
358
Use descriptive variable names to increase readability.
359
359
**Why?** It makes the code easier to follow and update.
360
360
361
-
<spanstype="color:green">
361
+
<spanstyle="color:green">
362
362
GOOD:
363
363
</span>
364
364
@@ -379,7 +379,7 @@ BAD:
379
379
When working with input type `checkbox`, do not use the `click` action; use `checkOption` or `uncheckOption` instead.
380
380
**Why?** A click does not make it clear what the ending state will be; it will simply toggle the current state. Using the proper actions will ensure the expected state of the checkbox.
0 commit comments