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"`

* `codecept console acceptance` - starts acceptance suite environment. If you use WebDriver you can manipulate browser with Codeception commands.

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`

Generates empty environment configuration file into envs dir:

* `codecept g:env firefox`

Required to have `envs` path to be specified in `codeception.yml`

Creates default config, tests directory and sample suites for current project.

Use this command to start building a test suite.

By default it will create 3 suites **Acceptance**, **Functional**, and **Unit**.

* `codecept bootstrap` - creates `tests` dir and `codeception.yml` in current dir.

* `codecept bootstrap --empty` - creates `tests` dir without suites

* `codecept bootstrap --namespace Frontend` - creates tests, and use `Frontend` namespace for actor classes and helpers.

* `codecept bootstrap --actor Wizard` - sets actor as Wizard, to have `TestWizard` actor in tests.

* `codecept bootstrap path/to/the/project` - provide different path to a project, where tests should be placed

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`

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`

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

Generates skeleton for Unit Test that extends `Codeception\TestCase\Test`.

* `codecept g:test unit User`

* `codecept g:test unit "App\User"`

* `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

Prints all steps from all Gherkin contexts for a specific suite

{% highlight yaml %}

codecept gherkin:steps acceptance

{% endhighlight %}

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`

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

Creates empty Helper class.

* `codecept g:helper MyHelper`

* `codecept g:helper "My\Helper"`

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

Shows step by step execution process for scenario driven tests without actually running them.

* `codecept dry-run acceptance`

* `codecept dry-run acceptance MyCest`

* `codecept dry-run acceptance checkout.feature`

* `codecept dry-run tests/acceptance/MyCest.php`