Workshop in English - US at Longhorn PHP Conference 2023
Track Name:
Ballroom C&D
Checkout the code: https://github.com/sketchings/symfony-codeception-demo
View Slides: https://gist.github.com/sketchings/5b20efa0a5cf735b75f215cc06a2058d
Short URL: https://joind.in/talk/342c5
(QR-Code (opens in new window))
Why should I add another layer to make testing even more complicated?
Behavior Driven Development (BDD) is a popular software development methodology. BDD is an extension of Test Driven Development (TDD) inspired by Agile practices. But is the added layer really worth it? The primary reason to choose BDD as your development process is to break down communication barriers between business and technical teams. BDD encourages automated testing to verify all documented features of a project from the beginning.
Narrow the idea of story BDD:
* describe features in a scenario with a formal text
* use examples to make abstract things concrete
* implement each step of a scenario for testing
* write actual code implementing the feature
By writing every feature in User Story format that is automatically executable as a test, we ensure that: businesses, developers, QAs, and managers are all on the same page. BDD encourages exploration and debate to formalize the requirements and features by writing the User Stories so everyone can understand. By making tests part of the User Story, BDD allows non-technical personnel to write (or edit) Acceptance tests. This procedure also ensures that everyone in a team knows what was developed, what was not, what was tested, and what was not.
If you write your tests in a reusable way, it can often make your tests LESS complicated. Codeception collects and shares best practices and solutions for testing PHP web applications. With a flexible set of included modules, tests are easy to write, use, and maintain. Get started today writing your first BDD test.
Comments
Comments are closed.
The tutorial was very informative, but she copied and pasted code blocks from a location we didn't have access to, so it was tough to keep up.
having a gist to reference blocks of code, or sharing the finished setup. Loved how you started from scratch and used a demo site to help show how to start using this setup.
Also enjoyed the explanations of the different terms used. and where some could be defined differently between which project or team you are working on/with.
Great talk and introduction to this tricky to get started system. Thanks for the live code walk through, it really helped me understand BDD
Although I was not able to codeall parts as they were explained because of business reasons, I liked the tutorial a lot. We got a good overview, were made aware of some initial hiccups we can run in and the presenter announced that she will provide a more complete code example to us.