<li><a href="/docs/01-Introduction">Introduction</a></li><li><a href="/docs/02-GettingStarted">Getting Started</a></li><li><a href="/docs/03-ModulesAndHelpers">Modules And Helpers</a></li><li><a href="/docs/04-AcceptanceTests">Acceptance Tests</a></li><li><a href="/docs/05-FunctionalTests">Functional Tests</a></li><li><a href="/docs/06-UnitTests">Unit Tests</a></li><li><a href="/docs/07-AdvancedUsage">Advanced Usage</a></li><li><a href="/docs/08-CestFormat">Cest Format</a></li><li><a href="/docs/09-Data">Data</a></li><li><a href="/docs/10-WebServices">Web Services</a></li><li><a href="/docs/11-Codecoverage">Codecoverage</a></li>

<li><a href="/docs/modules/AMQP">AMQP</a></li><li><a href="/docs/modules/Cli">Cli</a></li><li><a href="/docs/modules/Db">Db</a></li><li><a href="/docs/modules/Dbh">Dbh</a></li><li><a href="/docs/modules/Doctrine1">Doctrine1</a></li><li><a href="/docs/modules/Doctrine2">Doctrine2</a></li><li><a href="/docs/modules/Filesystem">Filesystem</a></li><li><a href="/docs/modules/Kohana">Kohana</a></li><li><a href="/docs/modules/Laravel4">Laravel4</a></li><li><a href="/docs/modules/Memcache">Memcache</a></li><li><a href="/docs/modules/MongoDb">MongoDb</a></li><li><a href="/docs/modules/PhpBrowser">PhpBrowser</a></li><li><a href="/docs/modules/REST">REST</a></li><li><a href="/docs/modules/Redis">Redis</a></li><li><a href="/docs/modules/SOAP">SOAP</a></li><li><a href="/docs/modules/Selenium">Selenium</a></li><li><a href="/docs/modules/Selenium2">Selenium2</a></li><li><a href="/docs/modules/SocialEngine">SocialEngine</a></li><li><a href="/docs/modules/Symfony1">Symfony1</a></li><li><a href="/docs/modules/Symfony2">Symfony2</a></li><li><a href="/docs/modules/Unit">Unit</a></li><li><a href="/docs/modules/WebDebug">WebDebug</a></li><li><a href="/docs/modules/XMLRPC">XMLRPC</a></li><li><a href="/docs/modules/Yii1">Yii1</a></li><li><a href="/docs/modules/ZF1">ZF1</a></li><li><a href="/docs/modules/ZF2">ZF2</a></li><li><a href="/docs/modules/ZombieJS">ZombieJS</a></li>

<b>Selenium</b> or other backends. Codeception is

use \Codeception\Util\Stub;

</div>

title: Codeception 1.5.5 and Roadmap Announced

layout: post

date: 2013-02-28 01:03:50

Yes, here is a new version of Codception with more features and bugfixes in it.

We have a flexible relase cycle, so the new version comes when we have a set of updates that you might be needed.

We want to say "thank you" for all contributors, and for everyone who helps making Codeption better.

It's always nice to get pull requests or [follow discussions](https://github.com/Codeception/Codeception/issues/) in our issues secition.

So let us sum up the work was done during last 2 weeks and share it with you.

All codeception commands got `-c` option to provide a custom path to tests.

The exception is `bootstrap` command. It accepts a custom directory as a second argument:

{% highlight bash %}

php codecept.phar bootstrap ~/mynewproject

php codecept.phar generate:cept acceptance Login -c ~/mynewproject

php codecept.phar generate:test unit MyFirstTest -c ~/mynewproject

php codecept.phar run -c ~/mynewproject

php codecept.phar generate:scenarios acceptance -c ~/mynewproject

{% endhighlight %}

Alternatively you may specify path to `codeception.yml` file in `-c` option: `php codecept.phar run -c ~/mynewproject/codeception.yml`

Thus, you don't need to keep your `codecept.phar` in the root of your project anymore. Use `-c` option and one local runner for all your projects.

Skipping and marking tests of incomplete was improved. We did a new solid implementation for it (it was very basic in `1.5.4`).

Now If a test is marked to skip, no modules will be touched.

{% highlight php %}

$scenario->skip('this is not ready yet, move along');

$I = new WebGuy($scenario);

$I->wanTo('do something, but I would rather not');

$I->amOnPage('/');

//.....

?>

{% endhighlight %}

This feature required to rework some core classes (like Step and TestCase and Scenario) but hopefully we simplified our code.

* `acceptPopup` with Selenium 2 does not trigger Exception any more

* error handling was improved to skip blocked with `@` alerts, yet to throw `ErrorException` for notices, warnings, errors.

* ZombieJS configuration was fixed. Now the `url` parameter is required to specify app's local url.

* REST `seeStatusCodeIs` method works correctly with Symfony2 now.

[redownload](http://codeception.com/thanks.html) your `codeception.phar` for update:

{% highlight bash %}

wget http://codeception.com/codecept.phar -O codecept.phar

{% endhighlight %}

for composer version

{% highlight bash %}

$ php composer.phar update

{% endhighlight %}

For the first time we will announce the roadmap for Codeception. Actually we need your opinion: what features you'd like to see in new releases, and what things can be postponed. The list below is not a precise plan, but just a list of features we have in mind:

* Make a PageObject pattern first-class citizen in Codeception. Add generators and guides to use PageObjects (for acceptance tests).

* Multiple sessions for tests execution ([see discission on GitHub](https://github.com/Codeception/Codeception/issues/154))

* **Silex**, **Laravel 4**, **Zend Framework 2**, **Drupal 8**, **Phalcon** integrations. The key problem here: we can't do this on our own. We need a real users of these frameworks, to create integration and test it on their projects. We have reworked [functional testing guide](http://codeception.com/docs/05-FunctionalTests) to help you with this. Also use GitHub or personal contacts if you want to make a module.

* **Scenario Unit Tests to be rethinked**. We have 2 options here: dump scenario driven unit tests (or mark them as deprecated) or rework them. Actually we need your real opinion. [Here is an example of what new Cests may look like](https://gist.github.com/DavertMik/5042537). They will dramatically improve the way you work with mocks and stubs in PHP. But will you use it? Please, let us know what you think.

To summarize: we'd appreciate contributions, feedbacks and ideas for next releases.

---

title: Codeception 1.5.6

layout: post

date: 2013-03-10 01:03:50

---

Codeption 1.5.6 released with varous fixes to Selenium2 module (popups, screenshots) an other bugfixes.

We added a bunch of tests for Selenium2 and they are runnng on TravisCI.

Also, Codeception is now compatble with Symony 2.2. And few features were intrduced.

Very basic implementation of fixtures was added to Db and Mongo modules.

Now you can write something like:

{% highlight php %}

<?php

// for Db

$I->haveInDatabase('users', array('name' => 'davert'));

// for Mongo

$I->haveInCollection('users', array('name' => 'davert'));

?>

{% endhighlight %}

to add data for a test. For Db module, the inserted record will be cleaned up on text test, even If `cleanup` option is set to false. So `haveInDatabase` method cleans data after itself.

Something similar exists for Doctrine2 module. Yet, it looks not like for Db and Mongo implementation:

{% highlight php %}

<?php

$I->persistEntity(new \Entity\User, array('name' => 'Miles'));

{% endhighlight %}

### Basic Fixtures

Very basic implementation of fixtures was added to Db and Mongo modules.

Now you can write something like:

{% highlight php %}

<?php

// for Db

$I->haveInDatabase('users', array('name' => 'davert'));

// for Mongo

$I->haveInCollection('users', array('name' => 'davert'));

?>

{% endhighlight %}

to add data for a test. For Db module, the inserted record will be cleaned up on text test, even If `cleanup` option is set to false. So `haveInDatabase` method cleans data after itself.

Something similar exists for Doctrine2 module. Yet, it looks not like for Db and Mongo implementation:

{% highlight php %}

<?php

$I->persistEntity(new \Entity\User, array('name' => 'Miles'));

{% endhighlight %}

### Error Handling

From now on you can set custom error handling parameters per suite or globally.

{% highlight yaml %}

class_name: WebGuy

modules:

enabled: [PhpBrowser, WebHelper]

error_level: "E_ALL & ~E_STRICT & ~E_DEPRECATED"

{% endhighlight %}

Actually, `E_ALL & ~E_STRICT & ~E_DEPRECATED` is default error level for now. This may be changed in future.

### Bugfixes

* popups and modals in Selenium2 are fully tested and work correctly now

* screenshots in Selenium2 module is saved correctly

* `seeInField` method works correctly even if field is not in form

* fix to AMQP module to push message to queue

* Symfony 2.2 compatibility

### Update

[redownload](http://codeception.com/thanks.html) your `codeception.phar` for update:

{% highlight bash %}

wget http://codeception.com/codecept.phar -O codecept.phar

{% endhighlight %}

for composer version

{% highlight bash %}

$ php composer.phar update

{% endhighlight %}

title: Codeception 1.5.6

layout: post

date: 2013-03-10 01:03:50

Codeption 1.5.6 released with varous fixes to Selenium2 module (popups, screenshots) an other bugfixes.

We added a bunch of tests for Selenium2 and they are runnng on TravisCI.

Also, Codeception is now compatble with Symony 2.2. And few features were intrduced.

Very basic implementation of fixtures was added to Db and Mongo modules.

Now you can write something like:

{% highlight php %}

$I->haveInDatabase('users', array('name' => 'davert'));

// for Mongo

$I->haveInCollection('users', array('name' => 'davert'));

?>

{% endhighlight %}

to add data for a test. For Db module, the inserted record will be cleaned up on text test, even If `cleanup` option is set to false. So `haveInDatabase` method cleans data after itself.

Something similar exists for Doctrine2 module. Yet, it looks not like for Db and Mongo implementation:

{% highlight php %}

$I->persistEntity(new \Entity\User, array('name' => 'Miles'));

{% endhighlight %}

### Error Handling

From now on you can set custom error handling parameters per suite or globally.

{% highlight yaml %}

class_name: WebGuy

modules:

enabled: [PhpBrowser, WebHelper]

error_level: "E_ALL & ~E_STRICT & ~E_DEPRECATED"

{% endhighlight %}

Actually, `E_ALL & ~E_STRICT & ~E_DEPRECATED` is default error level for now. This may be changed in future.

### Bugfixes

* popups and modals in Selenium2 are fully tested and work correctly now

* screenshots in Selenium2 module is saved correctly

* `seeInField` method works correctly even if field is not in form

* fix to AMQP module to push message to queue

* Symfony 2.2 compatibility

### Update

[redownload](http://codeception.com/thanks.html) your `codeception.phar` for update:

{% highlight bash %}

wget http://codeception.com/codecept.phar -O codecept.phar

{% endhighlight %}

for composer version

{% highlight bash %}

$ php composer.phar update

{% endhighlight %}

layout: post

title: Scenario Unit Tests Deprecation Announcement

date: 2013-03-18 22:03:50

We decided to get rid of the scenario unit tests. The main reason is: the concept was interesting, but current realization is a bit outdated.

It would take to much time to maintain and support them. Hopefully, not to much developers used them anyway ) They are cool if you are dealing with mocks in your tests, but they don't bring any value if you write a plain unit test. We've seen too much improperly written unit tests in Cest format so we'd actually recommend you to switch to classical unittests with codeGuy helpers.

So now recommended are Codeception driven unit tests, in PHPUnit like format:

{% highlight php %}

$this->user = new User();

}

function testUserIsSaved()

{

$this->user->name = 'miles';

$this->user->save();

$this->codeGuy->seeInDatabase('users', array('name' => 'miles'));

}

}

?>

{% endhighlight %}

If you still interested in scenario driven tests, leave your feedback or even propose your concept. [Here is one of them]( https://gist.github.com/DavertMik/5042537)

The real idea behind scenario driven unit tests to have code well described in a human language. This is especially useful when dealing with mocks and stubs. In this case we can implement some 'magic' methods that allows us to simplify manipulation with code and write only definitions. What methods do we need, what methods do we test, what we expect to see. No unnescessary technlical details. Only logic and dependencies.

The Cest format itself is not going to be deprecated. It would be proposed to use in functional or acceptance tests as an alternative. If you like to write tests in a class (rather then plain PHP file), please use Cest format. More announcement comes on this soon. Expect a new vewsion.

Scenario driven tests <strong>will be removed in 1.7 version</strong> of Codeception.

So migrate them to regular unit tests.