With the first argument you can run all tests from one suite.

To limit tests run to a single class, add a second argument. Provide a local path to the test class, from the suite directory.

You can further filter which tests are run by appending a method name to the class, separated by a colon (for Cest or Test formats):

php codecept run tests/acceptance/SignInCest.php:^anonymousLogin$

You can provide a directory path as well. This will execute all tests from the backend dir:

Using regular expressions, you can even run many different test methods from the same directory or class. For example, this will execute all tests from the backend dir beginning with the word login:

{% highlight bash %}

php codecept run tests/acceptance/backend:^login

{% endhighlight %}

$I->fillField('body', 'Hello all!');

Running those steps takes time, and in the case of Selenium tests (which are slow by themselves) that time loss can become significant.

Codeception allows you to share cookies between tests, so a test user can stay logged in for other tests.

Let's improve the code of our `login` method, executing the form submission only once and restoring the session from cookies for each subsequent login function call.

Please note that session restoration only works for `WebDriver` modules (modules implementing `Codeception\Lib\Interfaces\SessionSnapshot`).

StepObjects are great if you need some common functionality for a group of tests. Let's say you are going to test an admin area of a site. Probably, you won't need the same actions from admin area while testing the frontend, so it's a good idea to move these admin-specific tests into their own class. We will call such a class a StepObject.

Lets create an Admin StepObject with the generator:

You can supply optional action names. Enter one at a time, followed by a newline. End with an empty line to continue to StepObject creation.

This will generate a class in `/tests/_support/Step/Acceptance/Admin.php` similar to this:

Use <a href="http://codeception.com/docs/06-ModulesAndHelpers#Dynamic-Configuration-With-Params">module params</a> to set database credentials from environment variables or from application configuration files.

* `param` $char string|array Can be char or array with modifier. You can provide several chars.

* cleanup: true - whether the dump should be reloaded before each test

* url: `string`, default `http://localhost` - The application URL

* app - `\Laravel\Lumen\Application` instance

* client - `\Symfony\Component\BrowserKit\Client` instance

* ORM - include only haveRecord/grabRecord/seeRecord/dontSeeRecord actions

Set the authenticated user for the next request.

This will not persist between multiple requests.

* `param` \Illuminate\Contracts\Auth\Authenticatable

Check that user is not authenticated.

__not documented__

__not documented__

Checks that user is authenticated.

#### setApplication

* `param \Laravel\Lumen\Application` $app