This week we looked into Cucumber’s Gherkin, a language syntax specification that accelerates behavior-driven development and allows us to specify features.
The syntax is not hard to learn. We were able to outline our first feature file within 15 minutes. However, we noticed that we can’t really specify many feature files since most of our app reads data from external services, like RaPla, OpenMensa.org, and others. So what’s left? We specified a feature file for the betting feature:
https://dev.azure.com/foodies-inc/foody/_wiki/wikis/foody.wiki/10/Bets
If you have any suggestions, please let us know below.
Cheers
2 replies on “Gherkin 🥒”
Hey Foodies Inc.,
I think you have identified the core scenarios which your application has to handle. Your .feature file look good so far and you have paid special attention to the various edge cases that can occur.
Keep it going, I look forward to seeing your next blog entries!
Stefan@GameBase
Hello Foodies-Team,
Your feature files look good to us and cover every important test case.
The scenarios are easy to read and show that you understand how feature files work.
It would have been nice if you added a little preview (e.g. a GIF or some kind of video) of the testing process to show us how exactly your tests work.
Your LogicGame Team