* Unified bootstrap file loading

* Deprecated configuring bootstrap for all suites implicitly

* Added `--bootstrap` option to `run`

* **[Asserts]** Added specialized assertEquals methods

* **[Doctrine2]** Added support for Expression and Criteria objects in queries by **[alexkunin](https://github.com/alexkunin)**

* **[Doctrine2]** Added fixture support by **[alexkunin](https://github.com/alexkunin)**

* **[Doctrine2]** added refreshEntities and clearEntityManager methods by **[alexkunin](https://github.com/alexkunin)**

* **[Doctrine2]** implement recursive entity creation by **[alexkunin](https://github.com/alexkunin)**

* **[Doctrine2]** properly handle non-typical primary keys in haveInRepository by **[alexkunin](https://github.com/alexkunin)**

* **[Doctrine2]** merge functionality of persistEntity into haveInRepository by **[alexkunin](https://github.com/alexkunin)**

* **[Doctrine2]** deprecated persistEntity method by **[alexkunin](https://github.com/alexkunin)**

* **[Doctrine2]** Make haveInRepository support constructor parameters by **[burned42](https://github.com/burned42)**

* **[Symfony]** Fixed symfony 4.3 deprecation message removal by **[juntereiner](https://github.com/juntereiner)**

* **[Yii2]** Allow to preserve session with recreateApplication enabled by **[Slamdunk](https://github.com/Slamdunk)**

* **[Docs]** Documentation updates by **[Nebulosar](https://github.com/Nebulosar)** and **[mikehaertl](https://github.com/mikehaertl)**

* **[Docker]** Changed base image to 7.3-cli by **[OneEyedSpaceFish](https://github.com/OneEyedSpaceFish)**

* Robo build:phar command can be used for building custom phar files again

* Improved file path detection for groups [#5609](https://github.com/Codeception/Codeception/issues/5609) by **[adaniloff](https://github.com/adaniloff)**

* Shortened error output of unexpected exit to one line by **[Slamdunk](https://github.com/Slamdunk)**

* Fixed composer.json of codeception/base package

| | Unit Tests | Functional Tests | Acceptance Tests

| Additional software required | None | None | Selenium for browser testing</ul> |

| Speed | Fast | Fast | Slow |

One of the main advantages of Codeception is that you don't have to decide on just *one* type of testing. You should have all three!

How does your client, manager, tester, or any other non-technical person know your website is working? By opening the browser, accessing the site, clicking on links, filling in the forms, and actually seeing the content on a web page. They have no idea of the programming language, framework, database, web-server,

$I->submitForm('#signup', [

'username' => 'MilesDavis',

'email' => 'miles@davis.com'

]);

What if you could check our application without running it on a server?

That way you could see detailed exceptions on errors, have our tests run faster, and check the database against predictable and expected results. That's what functional tests are for.

For functional tests, you emulate a web request (`$_GET` and `$_POST` variables) which returns the HTML response. Inside a test, you can make assertions about the response, and you can check if the data was successfully stored in the database.

For functional tests, your application needs to be structured in order to run in a test environment. Codeception provides connectors to all popular PHP frameworks.

> This looks very similar to acceptance tests. The behavior is the same, however, the test is executed inside PHP without launching a browser.

$this->tester->seeInDatabase('users', [

'name' => 'Miles',

'surname' => 'Davis'

]);

All Codeception tests are written in a descriptive manner.

* **Grabbers** take information. The return value of those are meant to be saved as variables and used later. Example:

One of the main concepts of Codeception is representation of tests as actions of a person.We have a UnitTester, who executes functions and tests the code. We also have a FunctionalTester, a qualified tester,

Methods of actor classes are generally taken from [Codeception Modules](http://codeception.com/docs/06-ModulesAndHelpers). Each module provides predefined actions for different testing purposes, and they can be combined to fit the testing environment.

{% endhighlight %}

{% endhighlight %}

{% endhighlight %}

{% endhighlight %}

### Common Cases

<<<<<<< HEAD

Let's see how common problems of acceptance testing can be solved with Codeception.

#### Authorization

=======

Let's see how common problems of acceptance testing can be solved with Codeception. We will need to update actor class (whcih is AcceptanceTester) in our case to add a new action.

#### Login

>>>>>>> 82997221b762bc09876379f9f30906c9d364a4f5

It is recommended to put widely used actions inside an Actor class. A good example is the `login` action

which would probably be actively involved in acceptance or functional testing:

{% highlight php %}

$I->amOnPage('/login');

$I->submitForm('#loginForm', [

'login' => $name,

'password' => $password

]);

$I->see($name, '.navbar');

}

}

{% endhighlight %}

Now you can use the `login` method inside your tests:

{% highlight php %}

$I->login('miles', '123456');

{% endhighlight %}

However, implementing all actions for reuse in a single actor class may lead to

breaking the [Single Responsibility Principle](http://en.wikipedia.org/wiki/Single_responsibility_principle).

<<<<<<< HEAD

#### Session Snapshot

=======

#### Single Login

>>>>>>> 82997221b762bc09876379f9f30906c9d364a4f5

If you need to authorize a user for each test, you can do so by submitting the login form at the beginning of every test.

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:

{% highlight php %}

if ($I->loadSessionSnapshot('login')) {

return;

}

// logging in

$I->amOnPage('/login');

$I->submitForm('#loginForm', [

'login' => $name,

'password' => $password

]);

$I->see($name, '.navbar');

// saving snapshot

$I->saveSessionSnapshot('login');

}

{% endhighlight %}

Note that session restoration only works for `WebDriver` modules

(modules implementing `Codeception\Lib\Interfaces\SessionSnapshot`).

{% endhighlight %}