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
-[Write and run your first test suite](#write-and-run-your-first-test-suite)
45
45
-[Export tests report](#export-tests-report)
@@ -696,9 +696,9 @@ Example:
696
696
# Remaining steps in this context will not be executed
697
697
```
698
698
699
-
#### Custom assertions
699
+
#### User assertions
700
700
701
-
It is possible to use the [user defined executors syntax](#user-defined-executors) and prefixing your executor name with `Should` to create a new custom assertion keyword.
701
+
It is possible to use the [user defined executors syntax](#user-defined-executors) and prefixing your executor name with `Should` to create a new "user assertion" keyword.
702
702
703
703
Example:
704
704
```yml
@@ -712,7 +712,7 @@ steps:
712
712
713
713
You may also include additional steps like a regular user defined executor.
714
714
715
-
Custom assertions are executed in an entirely clean context, containing only the following variables:
715
+
User assertions are executed in an entirely clean context, containing only the following variables:
716
716
- `a`: the left operand
717
717
- `b`: the (first) right operand
718
718
- `argv`: the rights operands
@@ -723,7 +723,7 @@ input:
723
723
test: "{{.argv.argv1}}"
724
724
```
725
725
726
-
To call a registered custom assertions, just use its registered name in the `assertions` array, like any built-in assertion keyword.
726
+
To call a registered user assertions, just use its registered name in the `assertions` array, like any built-in assertion keyword.
0 commit comments