Can be configured in suite config:

Can be configured in suite config:

Multiple parameters can be passed as array:

The same way we tested a web site, Codeception allows you to test web services. They are very hard to test manually, so it's a really good idea to automate web service testing. We have SOAP and REST as standards, which are represented in corresponding modules, which we will cover in this chapter.

We will put all the api tests there.

The REST web service is accessed via HTTP with standard methods: `GET`, `POST`, `PUT`, `DELETE`. They allow users to receive and manipulate entities from the service. Accessing a WebService requires an HTTP client, so for using it you need the module `PhpBrowser` or one of framework modules set up. For example, we can use the `Symfony` module for Symfony2 applications in order to ignore web server and test web service internally.

actor: ApiTester

Once we have configured our new testing suite, we can create the first sample test:

We need to specify the `url` parameter in the acceptance suite config:

actor: AcceptanceTester

modules:

enabled:

class SigninCest

Conditional assertions are disabled in bootstrap setup. To enable them you should add corresponding step decorators to suite config:

step_decorators:

- \Codeception\Step\ConditionalAssertion

Retries are disabled by default. To enable them you should add retry step decorators to suite config:

step_decorators:

- \Codeception\Step\Retry

A/B testing is disabled by default. To enable it you should add corresponding step decorators to suite config:

There are several ways to execute a bunch of tests. You can run tests from a specific directory:

You can execute one (or several) specific groups of tests:

We will assume that we will use scenarios in feature files for acceptance tests, so feature files to be placed in `acceptance` suite directory:

Generated template will look like this:

We can test this scenario by executing it in dry-run mode. In this mode test won't be executed (actually, we didn't define any step for it, so it won't be executed in any case).

checkout: order several products

Signature: checkout:order several products

Scenario --

In order to buy product

As a customer

If you want to run a specific suite from the application you can execute:

In this example we will assume that there is `frontend/codeception.yml` configuration file

and that we will execute the unit tests for only that app.

Provide a class name as a parameter:

A list of tests for the group can be passed from a Group file. It should be defined in plain text with test names on separate lines:

A group file can be included by its relative filename:

It is possible to run specific suites from included applications:

Tasks from `\Codeception\Task\SplitTestsByGroups` will generate non-intersecting group files. You can either split your tests by files or by single tests:

// Split your tests by files

$this->taskSplitTestFilesByGroups(5)

->projectRoot('.')

->groupsTo('tests/Support/Data/paracept_')

->run();

/*

// Split your tests by single tests (alternatively)

$this->taskSplitTestsByGroups(5)

->projectRoot('.')

->groupsTo('tests/Support/Data/paracept_')

->run();

*/

for ($i = 1; $i <= 5; $i++) {

$parallel->process(

$this->taskCodecept() // use built-in Codecept task

->group("paracept_$i") // for all paracept_* groups

->xml("tests/_log/result_$i.xml") // save XML results

);

Codeception can generate a PageObject class for you with command:

Lets create an Admin StepObject with the generator:

Add action to StepObject class (ENTER to exit): loginAsAdmin

Add action to StepObject class (ENTER to exit):