Cucumber’s popularity might give the impression it’s an easy tool to master. It ain’t! Many experienced Cucumber users have the bumps and bruises to prove it. Matt, Steve, and Aslak from the core Cucumber team discuss writing good gherkin and avoiding common pitfalls.

We’ll unpick why it’s important to write your gherkin before you write the code, consider if you should ever delete scenarios, and give tips on incorporating your team’s different perspectives into maintainable, predictable cukes!

We also wrote up this conversation into two blog posts. Read Part 1 and Part 2.

You can also listen and download the podcast on iTunes and Stitcher.

Subscribe and share your thoughts in the comments or on Twitter