updated

Author: github-actions[bot]

docs/reference/Commands.md

@@ -5,61 +5,6 @@ title: Commands - Codeception - Documentation
 
 # Console Commands
 
-## 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`
-
-
-
-## GherkinSnippets
-
-Generates code snippets for matched feature files in a suite.
-Code snippets are expected to be implemented in Actor or PageObjects
-
-Usage:
-
-* `codecept gherkin:snippets acceptance` - snippets from all feature of acceptance tests
-* `codecept gherkin:snippets acceptance/feature/users` - snippets from `feature/users` dir of acceptance tests
-* `codecept gherkin:snippets acceptance user_account.feature` - snippets from a single feature file
-* `codecept gherkin:snippets acceptance/feature/users/user_accout.feature` - snippets from feature file in a dir
-
-
-
-## 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`
-
-
-
-## GenerateHelper
-
-Creates empty Helper class.
-
-* `codecept g:helper MyHelper`
-* `codecept g:helper "My\Helper"`
-
-
-
-
 ## Run
 
 Executes tests.
@@ -148,6 +93,16 @@ Options:
 
 
 
+## 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
+
+
+
 ## Bootstrap
 
 Creates default config, tests directory and sample suites for current project.
@@ -164,21 +119,32 @@ By default it will create 3 suites **Acceptance**, **Functional**, and **Unit**.
 
 
 
-## SelfUpdate
+## Build
 
-Auto-updates phar archive from official site: 'https://codeception.com/codecept.phar' .
+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.
 
-* `php codecept.phar self-update`
+* `codecept build`
+* `codecept build path/to/project`
 
-@author Franck Cassedanne <[email protected]>
 
 
 
-## GenerateGroup
+## GenerateTest
 
-Creates empty GroupObject - extension which handles all group events.
+Generates skeleton for Unit Test that extends `Codeception\TestCase\Test`.
 
-* `codecept g:group Admin`
+* `codecept g:test unit User`
+* `codecept g:test unit "App\User"`
+
+
+
+## GenerateHelper
+
+Creates empty Helper class.
+
+* `codecept g:helper MyHelper`
+* `codecept g:helper "My\Helper"`
 
 
 
@@ -195,27 +161,59 @@ codecept gherkin:steps acceptance
 
 
 
-## Init
+## GenerateSuite
 
+Create new test suite. Requires suite name and actor name
 
+* ``
+* `codecept g:suite api` -> api + ApiTester
+* `codecept g:suite integration Code` -> integration + CodeTester
+* `codecept g:suite frontend Front` -> frontend + FrontTester
 
-## GenerateEnvironment
 
-Generates empty environment configuration file into envs dir:
 
- * `codecept g:env firefox`
 
-Required to have `envs` path to be specified in `codeception.yml`
+## 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`
 
-## 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
+## GenerateGroup
+
+Creates empty GroupObject - extension which handles all group events.
+
+* `codecept g:group Admin`
+
+
+
+## GherkinSnippets
+
+Generates code snippets for matched feature files in a suite.
+Code snippets are expected to be implemented in Actor or PageObjects
+
+Usage:
+
+* `codecept gherkin:snippets acceptance` - snippets from all feature of acceptance tests
+* `codecept gherkin:snippets acceptance/feature/users` - snippets from `feature/users` dir of acceptance tests
+* `codecept gherkin:snippets acceptance user_account.feature` - snippets from a single feature file
+* `codecept gherkin:snippets acceptance/feature/users/user_accout.feature` - snippets from feature file in a dir
+
+
+
+## SelfUpdate
+
+Auto-updates phar archive from official site: 'https://codeception.com/codecept.phar' .
+
+* `php codecept.phar self-update`
+
+@author Franck Cassedanne <[email protected]>
 
 
 
@@ -229,59 +227,58 @@ Generates StepObject class. You will be asked for steps you want to implement.
 
 
 
-## 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.
 
 
 
-## ConfigValidate
+## GenerateEnvironment
 
-Validates and prints Codeception config.
-Use it do debug Yaml configs
+Generates empty environment configuration file into envs dir:
 
-Check config:
+ * `codecept g:env firefox`
 
-* `codecept config`: check global config
-* `codecept config unit`: check suite config
+Required to have `envs` path to be specified in `codeception.yml`
 
-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)
+## Clean
 
-* `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
+Recursively cleans `output` directory and generated code.
 
+* `codecept clean`
 
 
 
-## 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.
+## GenerateCest
 
-* `codecept build`
-* `codecept build path/to/project`
+Generates Cest (scenario-driven object-oriented test) file:
 
+* `codecept generate:cest suite Login`
+* `codecept g:cest suite subdir/subdir/testnameCest.php`
+* `codecept g:cest suite LoginCest -c path/to/project`
+* `codecept g:cest "App\Login"`
 
 
 
-## GenerateSuite
 
-Create new test suite. Requires suite name and actor name
 
-* ``
-* `codecept g:suite api` -> api + ApiTester
-* `codecept g:suite integration Code` -> integration + CodeTester
-* `codecept g:suite frontend Front` -> frontend + FrontTester
+## 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`
+
+
+
+## Init
 
 
 
@@ -296,35 +293,38 @@ Generates Feature file (in Gherkin):
 
 
 
-## DryRun
-
-Shows step by step execution process for scenario driven tests without actually running them.
+## ConfigValidate
 
-* `codecept dry-run acceptance`
-* `codecept dry-run acceptance MyCest`
-* `codecept dry-run acceptance checkout.feature`
-* `codecept dry-run tests/acceptance/MyCest.php`
+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:
 
-## Clean
+* `codecept config:validate -c path/to/another/config`: from another dir
+* `codecept config:validate -c another_config.yml`: from another config file
 
-Recursively cleans `output` directory and generated code.
+Check overriding config values (like in `run` command)
 
-* `codecept clean`
+* `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
 
 
 
 
-## GenerateCest
+## DryRun
 
-Generates Cest (scenario-driven object-oriented test) file:
+Shows step by step execution process for scenario driven tests without actually running them.
 
-* `codecept generate:cest suite Login`
-* `codecept g:cest suite subdir/subdir/testnameCest.php`
-* `codecept g:cest suite LoginCest -c path/to/project`
-* `codecept g:cest "App\Login"`
+* `codecept dry-run acceptance`
+* `codecept dry-run acceptance MyCest`
+* `codecept dry-run acceptance checkout.feature`
+* `codecept dry-run tests/acceptance/MyCest.php`