Happy Easter, everyone! Ok, not actually everyone, but Happy Easter to those who celebrate it this weekend. If you do (or even not), you probably will have free time to play with something new. And yes, by something we mean a beta version of Codeception 2.2!
We already announced lots of changes in Codeception:
but we forgot the most important one. It is Gherkin Support, which allows you to combine business requirements with functional testing. Yes,
*.feature files are now part of a family with Cest, Cept and Tests. Codeception is a tool for running all kind of tests and in this release we significantly improved test internal architecture and test formats.
But back to Gherkin.
Feature: ToDo items In order to get my tasks done As a motivated person I need to be able to organize my todo list Scenario: show current todos Given there are todo items: | Task | State | | make Gherkin PR | opened | | update docs | opened | | create examples | closed | When I open my todos Then I should see 2 todo items
Complete Guide on BDD with Codeception is not ready yest, but you can start with generating first feature file:
codecept g:feature <suiteName> <featureName>
We recommend to have a special features folder in acceptance or functional suite, so it could be symlinked to the
features dir in root of your project. This way non-technical users can esaily access feature files, without need to examine actual tests.
Next thing to do is to describe feature with scenarios. When you are done, prepare scenario steps for implementation be running
codecept gherkin:snippets <suiteName>
You will get a list of methods which should be included into your actor class (let’s say AcceptanceTester).
Then you should have it implemented. In theory, you can use any method of any class annotated with
@Then to be the step definition. So don’t worry you will end up with everything to put in one context, you will have option to use multiple contexts depending on role, tags, etc. More about it in BDD guide coming in next weeks.
For those of you, who set your dependencies as “codeception/codecepton:*” and (with no settings of
"minimum-stability": "stable" you will probably have some wonderful time once you get back from holidays. This release is considered minor, so it won’t break everything, but still has some breaking changes. We notified of breaking changes in earlier versions by “deprecation warnings”, and we actually removed lots of deprecated stuff. The most important breaking change is proper implementation of Conflicts API. Please make sure you are not using modules of the same kinds in your configs.
Codeception 2.2-beta is available for installation only via Composer:
composer require --dev "codeception/codeception:2.2.0-beta"
Next steps to do:
- Read the changelog. Check for all breaking changes. Probably you will need to update your Helper classes.
- Refer to updated module docs for this beta release in master branch.
Stable release will come in next week(s). The release date depends on reported issues and on progress of updating documentation.
Have nice weekends and testing time! We, Codeception team, hope you will love our product.
P.S. Reported issues should include a version. Pull Requests should be sent to master branch.