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
|`--force`| Forces test generation, regardless of the module merge order defined in the Magento instance. Example: `generate:tests --force`. |
123
123
|`-i,--time`| Set time in minutes to determine the group size when `--config=parallel` is used. The __default value__ is `10`. Example: `generate:tests --config=parallel --time=15`|
124
124
|`--tests`| Defines the test configuration as a JSON string.|
125
-
|`--debug=[<developer> or <none>]`|Set debug level to `default` when the option is not specified, to `developer` with `--debug developer` or `--debug`, to `none` with `--debugnone`||
125
+
|`--debug or --debug=[<none>]`|Performs schema validations on XML files </br> <br/> DEFAULT: `generate:tests` implicitly performs schema validation on merged files. It does not indicate the file name where the error is encountered. <br/> DEVELOPER: `--debug` performs per-file validation and returns additional debug information (such as the filename where an error occurred) when test generation fails because of an invalid XML schema. This option takes extra processing time. Use it after test generation has failed once.</br> <br/> NONE: `--debug=none`skips debugging during test generation. Added for backward compatibility, it will be removed in the next MAJOR release.</br>|
126
126
|`-r,--remove`| Removes the existing generated suites and tests cleaning up the `_generated` directory before the actual run. For example, `generate:tests SampleTest --remove` cleans up the entire `_generated` directory and generates `SampleTest` only.|
127
127
128
-
#### Debugging levels
129
-
130
-
You can run `generate:tests` with any of the following debug levels. XML schema validation errors will be logged as CRITICAL failures.
131
-
132
-
| Debug level | Description |
133
-
| ---| --- |
134
-
|`default``[generate:tests]`| Perform XML schema validation on merged files. Does not indicate the file name where the error is encountered. Use `developer` level for enhanced debugging. |
135
-
|`developer``[generate:tests --debug or generate:tests --debug developer]`| Returns additional debug information (such as the filename where an error occurred) when test generation fails because of an invalid XML schema. Note: This option takes extra processing time. Use it after test generation has failed once. |
136
-
|`none``[generate:tests --debug none]`| Skip debugging during test generation. Added for backward compatibility, it will be removed with the next MAJOR release.|
137
-
138
128
#### Examples of the JSON configuration
139
129
140
130
The configuration to generate a single test with no suites:
|`-k, --skip-generate`| Skips generating from the source XML. Instead, the command executes previously-generated groups of tests. |
307
297
|`-r, --remove`| Removes previously generated suites and tests before the actual generation and run. |
298
+
|`--debug or --debug=[<none>]`| <br/>Performs schema validations on XML files </br> <br/> DEFAULT: `run:group` implicitly performs schema validation on merged files. It does not indicate the file name where the error is encountered. <br/> DEVELOPER: `--debug` performs per-file validation and returns additional debug information (such as the filename where an error occurred) when test run fails because of an invalid XML schema. This option takes extra processing time. Use it after test run has failed once.</br> <br/> NONE: `--debug=none` skips debugging during test run. Added for backward compatibility, it will be removed in the next MAJOR release.</br>|
299
+
300
+
308
301
309
302
#### Examples
310
303
@@ -327,7 +320,7 @@ Generates and executes tests by name using Codeception.
|`-k, --skip-generate`| Skips generating from the source XML. Instead, the command executes previously-generated groups of tests. |
338
331
|`-r, --remove`| Remove previously generated suites and tests. |
332
+
|`--debug or --debug=[<none>]`|<br/>Performs schema validations on XML files </br><br/> DEFAULT: `run:test` implicitly performs schema validation on merged files. It does not indicate the file name where the error is encountered. <br/> DEVELOPER: `--debug` performs per-file validation and returns additional debug information (such as the filename where an error occurred) when test run fails because of an invalid XML schema. This option takes extra processing time. Use it after test run has failed once.</br><br/> NONE: `--debug=none` skips debugging during test run. Added forbackward compatibility, it will be removedin the next MAJOR release.</br>|
339
333
340
334
#### Examples
341
335
@@ -357,6 +351,12 @@ For more details about `failed`, refer to [Reporting][].
|`--debug or --debug=[<none>]`|<br/>Performs schema validations on XML files </br><br/> DEFAULT: `run:failed` implicitly performs schema validation on merged files. It does not indicate the file name where the error is encountered. <br/> DEVELOPER: `--debug` performs per-file validation and returns additional debug information (such as the filename where an error occurred) when test run fails because of an invalid XML schema. This option takes extra processing time. Use it after test run has failed once.</br><br/> NONE: `--debug=none` skips debugging during test run. Added forbackward compatibility, it will be removedin the next MAJOR release.</br>|
0 commit comments