Summary

In this chapter, we started by creating an easy-to-understand list of features and scenarios detailing what needs to be built, based on a Jira ticket. Before working on the solution code, we first started with a Gherkin feature called Inventory Clerk Registration. This feature can be read by anyone—even non-developers will be able to understand it. This feature explains how our system should behave. We then took that behavior and created simple and failing functional tests inside the Symfony application. Creating these failing tests gave us a list of things we need to build. We then proceeded to develop the solution to pass these failing functional tests. And finally, we wrote code to tell Behat the intricate steps to click a link or a button, and fill up fields. BDD and TDD are not just about writing automated tests—it’s about using them as a process to develop our solutions.

In the next chapter, we will continue building tests and solution code. We...