Skip to content

Commit d9bee7b

Browse files
committed
MQE-1800: Allow generate:tests to continue running even if one test fails generation
1 parent 2746837 commit d9bee7b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/commands/mftf.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -91,12 +91,12 @@ For more details about `failed`, refer to [Reporting][].
9191

9292
## Error tolerance during generation
9393

94-
Starting from version 3.2.0, MFTF will not fail right away when encounter generation errors.
95-
Instead MFTF will try to generate as many tests and suites as it can, log errors in `mftf.log` file and exit with non-zero generation status.
94+
Starting from version 3.2.0, MFTF will not fail right away when encountering generation errors.
95+
Instead, MFTF will generate as many tests and suites as it can, log errors to `mftf.log`, and exit with a non-zero generation status.
9696

9797
Note:
98-
- Not all errors are tolerable at generation. For example, schema validation error, parser error, WebApi authentication error will still cause `hard` failure with no test or suite generated.
99-
- Error tolerance in generation is mean to help local test development and testing. You should only expect to run generated tests locally. You must fix all generation errors to use other framework functionalities, pass static checks and to deliver MFTF tests.
98+
- Not all errors are tolerable at generation. For example, schema validation errors, parser errors, and WebApi authentication errors will cause `hard` failures, with no tests or suites being generated.
99+
- Error tolerance in generation is meant to help local test development and testing and is expected to be run locally. All generation errors must be fixed in order to use other framework functionality, pass static checks, and to deliver MFTF tests.
100100

101101
## Reference
102102

0 commit comments

Comments
 (0)