#gherkin

So, I needed to re-use features and saw that #gherkin does not have feature
level examples.

I wonder why that is?

Anyway, my #e2e test runner now has support for that.

https://github.com/NordicSemiconductor/cloud-e2e-bdd-test-runner-js/commit/ef338277b2603925d3b3c5be7488912f69fc8a03#diff-ea306231f3e59f77089f33442f3eb6a87dfacec6c1550eb1be2a2ad492c62c37

This is the test platform that we use to run the
@bifravst firmware on real hardware for every
commit.

See
https://bifravst.gitbook.io/bifravst/cat-tracker-firmware/firmwarecontinuousintegration

The tests are expressed using a #BDD style, written in #Gherkin:
https://github.com/bifravst/firmware/pull/82/files#diff-8140b13bf416d834ea873f009052f8121e7080e3fb6a4b6d9f00b20adbdd6114

I've now written the first #gherkin #bdd features for testing the
@bifravst firmware on real hardware:
https://github.com/bifravst/firmware/blob/d3903b83c5aa3f75acedcc79d7171c9786241c9f/features/RunFirmware.feature

I think that's a good way to express what should happen when the firmware is
running.

Here is another example of a feature:
https://github.com/bifravst/firmware/blob/d3903b83c5aa3f75acedcc79d7171c9786241c9f/features/CheckModemFirmware.feature

Oh nice! @HonestCodeio wants to visualise
the implemented features of your software based on test runs using #gherkin. I
have to check that out!
https://twitter.com/HonestCodeio/status/854746457664098308