but with tests you can cover the most important parts of your app and at least be sure they work as predicted.

There are plenty of ways to test your application.

For web applications, testing just the controller and/or the model doesn't prove that your application is working.

To test the behavior of your application as a whole, you should write functional or acceptance tests.

you can be sure that some deeply hidden feature still works, even if it was not covered by functional or acceptance tests.

This also shows care in producing stable and testable code.

you can continue doing so. Codeception has no problem executing standard PHPUnit tests,

but, additionally, Codeception provides some well-built tools to make your unit tests simpler and cleaner.

and bootstrapped your first test suites. Codeception has generated three of them: unit, functional, and acceptance.

with names corresponding to these suites: `unit`, `functional`, `acceptance`. Suites are independent groups of tests with a common purpose.

who tests the application as a whole, with knowledge of its internals. Lastly we have an AcceptanceTester, a user who works with our application

through an interface that we provide.

Codeception tries to solve 90% of possible testing issues in its modules, so you don't have to reinvent the wheel.

We think that you can spend more time on writing tests and less on writing support code to make those tests run.

By default, AcceptanceTester relies on PhpBrowser module, which is set in the `tests/acceptance.suite.yml` configuration file:

{% endhighlight %}

## Interactive Pause

## BDD

Codeception allows execution of user stories in Gherkin format in a similar manner as is done in Cucumber or Behat.

## Configuration

{% endhighlight %}

### Reports

| JavaScript | No | Yes |

| `see`/`seeElement` checks if… | …text is present in the HTML source | …text is actually visible to the user |

| Access to HTTP response headers and status codes | Yes | No |

| Speed | Fast | Slow |

We will start writing our first acceptance tests with PhpBrowser.

This is the fastest way to run acceptance tests since it doesn't require running an actual browser.

We use a PHP web scraper, which acts like a browser: It sends a request, then receives and parses the response.

Common PhpBrowser drawbacks:

{% endhighlight %}

which may help you to generate complex XPath locators.

For instance, it can easily allow you to click an element on the last row of a table:

> Alternatively, Selenium Server can be installed manually. [Download it](https://www.selenium.dev/downloads/) from the official site and launch a server with Java: `java -jar selenium-server-....jar`. In this case ChromeDriver and GeckoDriver must be installed separately.

### Configuration

{% endhighlight %}

Please note that actions executed in a browser will behave differently. For instance, `seeElement` won't just check that the element exists on a page,

but it will also check that element is actually visible to the user:

{% endhighlight %}

In this case, we are waiting for the 'agree' button to appear and then click it. If it didn't appear after 30 seconds,

If you don't know what exact element you need to wait for, you can simply pause execution with using `$I->wait()`

It is possible to wait for elements pragmatically.

If a test uses element which is not on a page yet, Codeception will wait for few extra seconds before failing.

Codeception enables implicit wait only when searching for a specific element and disables in all other cases. Thus, the performance of a test is not affected.

SmartWait can be enabled by setting `wait` option in WebDriver config. It expects the number of seconds to wait. Example:

{% endhighlight %}

#### A/B Testing

Additional debugging features by Codeception:

### Common Cases

{% endhighlight %}

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

#### Single Login

By default, WebDriver module is configured to automatically start browser before the test and stop afterward.

However, this can be switched off with `start: false` module configuration.

WebDriver module provides advanced methods for the browser session, however, they can only be used from Helpers.

## Error Reporting

Writing acceptance tests with Codeception and PhpBrowser is a good start.

You can easily test your Joomla, Drupal, WordPress sites, as well as those made with frameworks.

Writing acceptance tests is like describing a tester's actions in PHP. They are quite readable and very easy to write.

The module uses the Symfony Profiler to provide additional information and assertions.

### Laravel5

{% highlight yaml %}

### Zend Framework 2

{% highlight yaml %}

### Zend Expressive

{% highlight yaml %}

{% endhighlight %}

## Writing Functional Tests

with the `PhpBrowser` module enabled. All framework modules and the `PhpBrowser` module share the same methods

and the same engine.