Why you can't write scenarios in Jam
  March 15, 2019

At least, not yet.

A lot of people who are new to Jam ask us: Why can't we write scenarios in the tool?

Here's why: We have a firm opinion that there is a right way and a wrong way to do BDD, and the wrong way involves people using Gherkin to throw a specification over the wall at their development team.

Yes, Jam's goal is to make BDD inclusive and accessible to everyone. We do want your business analyst to ❤️ ️️️living documentation after working with Jam. Ultimately, we do want them have the freedom to edit and even write new scenarios from within the tool.

But let's start with the basics.

Embrace your ignorance

BDD is all about learning early. About deliberate discovery. About embracing your ignorance.

If you want to learn early about what you don't know, a really good way to do that is to have the person with the most to learn, write the scenarios.

That's why, instead of building a way for you to write scenarios, we prioritised developing a way for you to get feedback. Jam lets you publish your features so that your team can read and comment on them, inline, letting you iterate and reach agreement about what you're supposed to be building.

Comments in Cucumber Jam

Like what you see? Jam is free for teams of up to three people, forever, and $10 / person / month for bigger teams. By paying for Jam you're supporting the future of the Cucumber open source project.

Sign up here.