Implement Algorithmic Constituency #29
Description
Hello !
Would you be open to a test-suite written in plain english (and/or french) that would run integration tests on the API?
It would probably leverage behave.
These features act like an algorithmic constitution, sort of. It allows informatically illiterate people to read and contribute to the specifications of the application, as well as reporting bugs in a very convenient fashion. It shifts the sovereignty of the application from the developers to the community.
This is a pretty big and humiliating decision for developers to take, so we'd understand if you don't want to.
The features would look like this (working draft, in no way finished, and after re-reading it, it lacks some serious, but perhaps you'll get the idea) : https://framagit.org/limaju/limaju-server-features-fr/-/blob/master/10.fonctionnalites/20.voter-sur-un-scrutin.feature (we would rewrite them entirely for this project, and with consensus, of course)
From previous projects, we noted that the idiomatic features are best put in their own repository (one per language), and the feature runner, context and step defs in the project repository itself (here).
This allows Issues and Wiki and other repository goodies to be scoped correctly, and it also allows reusing the features on multiple projects, for example when this API will be rewritten in Go or Elixir or Scala to improve performance.
If you're interested in this, and you'd like to peer-code it, we can set this all up together in the near future, using one of the many screen-sharing, VoIP software available.