I found this to be the case when writing a Cucumber test for an Emacs package. You can see an example here: https://github.com/omouse/org-doing/blob/master/feat

I found this to be the case when writing a Cucumber test for an Emacs package. You can see an example here: https://github.com/omouse/org-doing/blob/master/features/org-doing.feature https://github.com/omouse/org-doing/blob/master/features/org... It was more helpful to write "Given I have an non-existent file" than to write "(not (file-exists-p org-doing-file))". One can be read by others who don't understand Emacs-Lisp and they'll understand the concept, while the latter can only be read by Emacs-Lisp developers. With the Gherkin syntax I'm free to move my tests over to another text editor and implement code that's specific to the text editor. For example, I could use my tests to implement the package for VIM or Atom (something I might do on a weekend). The best part is that you have the spec under version control and locked down instead of spread across. At work no one is really updating the functional spec of our project and it means we have information that's falling through the cracks and is in separate emails or IMs. Executable version-controlled specs have to be maintained but at least they're in one spot.