updated

Author: github-actions[bot]

docs/reference/Commands.md

@@ -5,13 +5,7 @@ title: Commands - Codeception - Documentation
 
 # Console Commands
 
-## GenerateScenarios
-
-Generates user-friendly text scenarios from scenario-driven tests (Cest).
-
-* `codecept g:scenarios acceptance` - for all acceptance tests
-* `codecept g:scenarios acceptance --format html` - in html format
-* `codecept g:scenarios acceptance --path doc` - generate scenarios to `doc` dir
+## Init
 
 
 
@@ -29,67 +23,77 @@ Usage:
 
 
 
-## GenerateTest
+## Console
 
-Generates skeleton for Unit Test that extends `Codeception\TestCase\Test`.
+Try to execute test commands in run-time. You may try commands before writing the test.
 
-* `codecept g:test unit User`
-* `codecept g:test unit "App\User"`
+* `codecept console acceptance` - starts acceptance suite environment. If you use WebDriver you can manipulate browser with Codeception commands.
 
 
 
-## SelfUpdate
+## ConfigValidate
 
-Auto-updates phar archive from official site: 'https://codeception.com/codecept.phar' .
+Validates and prints Codeception config.
+Use it do debug Yaml configs
 
-* `php codecept.phar self-update`
+Check config:
 
-@author Franck Cassedanne <franck@cassedanne.com>
+* `codecept config`: check global config
+* `codecept config unit`: check suite config
 
+Load config:
 
+* `codecept config:validate -c path/to/another/config`: from another dir
+* `codecept config:validate -c another_config.yml`: from another config file
 
-## GenerateFeature
+Check overriding config values (like in `run` command)
 
-Generates Feature file (in Gherkin):
+* `codecept config:validate -o "settings: shuffle: true"`: enable shuffle
+* `codecept config:validate -o "settings: lint: false"`: disable linting
+* `codecept config:validate -o "reporters: report: \Custom\Reporter" --report`: use custom reporter
 
-* `codecept generate:feature suite Login`
-* `codecept g:feature suite subdir/subdir/login.feature`
-* `codecept g:feature suite login.feature -c path/to/project`
 
 
 
+## Clean
 
-## CompletionFallback
+Recursively cleans `output` directory and generated code.
 
+* `codecept clean`
 
 
-## Console
 
-Try to execute test commands in run-time. You may try commands before writing the test.
 
-* `codecept console acceptance` - starts acceptance suite environment. If you use WebDriver you can manipulate browser with Codeception commands.
+## GenerateSnapshot
 
+Generates Snapshot.
+Snapshot can be used to test dynamical data.
+If suite name is provided, an actor class will be included into placeholder
 
+* `codecept g:snapshot UserEmails`
+* `codecept g:snapshot Products`
+* `codecept g:snapshot acceptance UserEmails`
 
-## GeneratePageObject
 
-Generates PageObject. Can be generated either globally, or just for one suite.
-If PageObject is generated globally it will act as UIMap, without any logic in it.
 
-* `codecept g:page Login`
-* `codecept g:page Registration`
-* `codecept g:page acceptance Login`
+## Build
 
+Generates Actor classes (initially Guy classes) from suite configs.
+Starting from Codeception 2.0 actor classes are auto-generated. Use this command to generate them manually.
 
+* `codecept build`
+* `codecept build path/to/project`
 
-## GenerateStepObject
 
-Generates StepObject class. You will be asked for steps you want to implement.
 
-* `codecept g:stepobject acceptance AdminSteps`
-* `codecept g:stepobject acceptance UserSteps --silent` - skip action questions
 
 
+## GenerateGroup
+
+Creates empty GroupObject - extension which handles all group events.
+
+* `codecept g:group Admin`
+
 
 
 ## Run
@@ -180,38 +184,44 @@ Options:
 
 
 
-## GherkinSteps
+## SelfUpdate
 
-Prints all steps from all Gherkin contexts for a specific suite
+Auto-updates phar archive from official site: 'https://codeception.com/codecept.phar' .
 
-{% highlight yaml %}
-codecept gherkin:steps acceptance
+* `php codecept.phar self-update`
 
-{% endhighlight %}
+@author Franck Cassedanne <franck@cassedanne.com>
 
 
 
+## GenerateTest
 
-## Clean
+Generates skeleton for Unit Test that extends `Codeception\TestCase\Test`.
 
-Recursively cleans `output` directory and generated code.
+* `codecept g:test unit User`
+* `codecept g:test unit "App\User"`
 
-* `codecept clean`
 
 
+## GenerateSuite
 
+Create new test suite. Requires suite name and actor name
 
-## GenerateHelper
+* ``
+* `codecept g:suite api` -> api + ApiTester
+* `codecept g:suite integration Code` -> integration + CodeTester
+* `codecept g:suite frontend Front` -> frontend + FrontTester
 
-Creates empty Helper class.
 
-* `codecept g:helper MyHelper`
-* `codecept g:helper "My\Helper"`
 
 
+## GenerateScenarios
 
+Generates user-friendly text scenarios from scenario-driven tests (Cest).
 
-## Init
+* `codecept g:scenarios acceptance` - for all acceptance tests
+* `codecept g:scenarios acceptance --format html` - in html format
+* `codecept g:scenarios acceptance --path doc` - generate scenarios to `doc` dir
 
 
 
@@ -227,37 +237,12 @@ Generates Cest (scenario-driven object-oriented test) file:
 
 
 
-## ConfigValidate
-
-Validates and prints Codeception config.
-Use it do debug Yaml configs
-
-Check config:
-
-* `codecept config`: check global config
-* `codecept config unit`: check suite config
-
-Load config:
-
-* `codecept config:validate -c path/to/another/config`: from another dir
-* `codecept config:validate -c another_config.yml`: from another config file
-
-Check overriding config values (like in `run` command)
-
-* `codecept config:validate -o "settings: shuffle: true"`: enable shuffle
-* `codecept config:validate -o "settings: lint: false"`: disable linting
-* `codecept config:validate -o "reporters: report: \Custom\Reporter" --report`: use custom reporter
-
-
-
-
-## Build
+## GenerateHelper
 
-Generates Actor classes (initially Guy classes) from suite configs.
-Starting from Codeception 2.0 actor classes are auto-generated. Use this command to generate them manually.
+Creates empty Helper class.
 
-* `codecept build`
-* `codecept build path/to/project`
+* `codecept g:helper MyHelper`
+* `codecept g:helper "My\Helper"`
 
 
 
@@ -278,24 +263,24 @@ By default it will create 3 suites **acceptance**, **functional**, and **unit**.
 
 
 
-## GenerateSuite
-
-Create new test suite. Requires suite name and actor name
+## GenerateStepObject
 
-* ``
-* `codecept g:suite api` -> api + ApiTester
-* `codecept g:suite integration Code` -> integration + CodeTester
-* `codecept g:suite frontend Front` -> frontend + FrontTester
+Generates StepObject class. You will be asked for steps you want to implement.
 
+* `codecept g:stepobject acceptance AdminSteps`
+* `codecept g:stepobject acceptance UserSteps --silent` - skip action questions
 
 
 
-## GenerateGroup
 
-Creates empty GroupObject - extension which handles all group events.
+## GeneratePageObject
 
-* `codecept g:group Admin`
+Generates PageObject. Can be generated either globally, or just for one suite.
+If PageObject is generated globally it will act as UIMap, without any logic in it.
 
+* `codecept g:page Login`
+* `codecept g:page Registration`
+* `codecept g:page acceptance Login`
 
 
 
@@ -309,6 +294,17 @@ Required to have `envs` path to be specified in `codeception.yml`
 
 
 
+## GenerateFeature
+
+Generates Feature file (in Gherkin):
+
+* `codecept generate:feature suite Login`
+* `codecept g:feature suite subdir/subdir/login.feature`
+* `codecept g:feature suite login.feature -c path/to/project`
+
+
+
+
 ## DryRun
 
 Shows step by step execution process for scenario driven tests without actually running them.
@@ -321,15 +317,19 @@ Shows step by step execution process for scenario driven tests without actually
 
 
 
-## GenerateSnapshot
+## GherkinSteps
 
-Generates Snapshot.
-Snapshot can be used to test dynamical data.
-If suite name is provided, an actor class will be included into placeholder
+Prints all steps from all Gherkin contexts for a specific suite
 
-* `codecept g:snapshot UserEmails`
-* `codecept g:snapshot Products`
-* `codecept g:snapshot acceptance UserEmails`
+{% highlight yaml %}
+codecept gherkin:steps acceptance
+
+{% endhighlight %}
+
+
+
+
+## CompletionFallback