a collection of small projects that demonstrate the use of Torshi (in stealth mode at the moment) in practice. At the moment, the focus is on translating Torshi specs into BDD specs written in Gherkin. Future examples will elaborate the use of Torshi specs as a means to practice rights-driven development and caring design.
The examples use Python and Behave. This is because Python code is usually quite readable, Python is already installed on many systems and even people who usually work in other languages often know a bit of Python.
Of course, Torshi is also written in Python but that does not mean the examples would need to be as Torshi is language-agnostic. However, from a maintenance point of view, it does make sense to use the same language.
Unfortunately, the choice means that, for the BDD part,we have to use the tooling available, which is not in an ideal state. The sections below describe choices made to set up a development environment using Behave, VSCode and the Cucumber extension for VSCode.
The latest published version of Behave v1.2.6 is from 2018 and it does not support
some important language constructs. In particular, it lacks support for the
Rule clause, which is important for the Example Mapping practice. As a
result, this example uses a developer version of Behave in the hope that a
version 1.2.7 will be released in the not too distant future.
The examples use {} in step definitions, which are positional step parameters
that both Cucumber and Behave support. This helps the Cucumber extension to
recognize step definitions.
Unfortunately, the alternative of using behave-cucumber-matcher does not
work with the developer version of Behave, which would mean not using Rule.
Its use also does not lead to step definitions being matched by the VSCode
extension. So, positional step parameters it is for the moment.
See this the description of Behave and the Cucumber VSCode Extension for more details.