View feature files page >>The Testing Team at A-LIGN decided to use the Gherkin language exclusively in its automated software testing. Every member of the team was supposed to use it for test case description, but in making the transition, some team members found it difficult to learn.
To get team members to get up to speed with Gherkin, and help them learn the specifics of using it at A-LIGN, I was asked to create a comprehensive guide. The testing team provided me with some information on its processes, and I got to work.
Using the team’s documentation tool, Confluence, I created a simple, straightforward structure for the guide. I incorporated an existing tutorial on the basics, then wrote my own tutorial on the central task when using Gherkin in automated testing: creating feature files.
To illustrate that process, I used code snippets that walked the reader through a typical testing scenario. I also included a page on best practices in using the language, compiled a glossary of Gherkin terms, and added some A-LIGN-specific syntax rules.
When the guide was finished, the team’s Senior Functional Tester, Julie Wayman, texted me through Slack: “Omg Chris I am loving this. This looks great. Thank you SO much for this by the way. We are super happy with the structure.”