https://github.com/jenmud/consensus
Consensus helps building and maintaining software by describing the expected behavior. It encourages participation from stakeholders, collaborators, and developers.
https://github.com/jenmud/consensus
bdd behavior-driven-development collaboration design maintenance stakeholders
Last synced: 4 months ago
JSON representation
Consensus helps building and maintaining software by describing the expected behavior. It encourages participation from stakeholders, collaborators, and developers.
- Host: GitHub
- URL: https://github.com/jenmud/consensus
- Owner: jenmud
- License: apache-2.0
- Created: 2023-01-10T09:48:19.000Z (about 3 years ago)
- Default Branch: master
- Last Pushed: 2024-07-27T07:51:14.000Z (over 1 year ago)
- Last Synced: 2024-08-27T09:08:48.735Z (over 1 year ago)
- Topics: bdd, behavior-driven-development, collaboration, design, maintenance, stakeholders
- Language: Go
- Homepage:
- Size: 69.6 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
### Consensus is still under development
# Consensus
Consensus helps building and maintaining software by describing the expected behavior.
It focuses on the high level expectations rather then low level details encouraging a wider
participation from stakeholders, collaborators, and developers.
It aims to provide a platform for creating a project as an `Epic` and instead of tickets/stories/tasks
as the traditional tracking systems do, it focuses on the expected behavior using the [Gherkin language](https://en.wikipedia.org/wiki/Cucumber_(software)#Gherkin_language). Ticket/stories/tasks become [Features](https://en.wikipedia.org/wiki/Cucumber_(software)#Features), [Scenarios](https://en.wikipedia.org/wiki/Cucumber_(software)#Scenarios) and [Steps](https://en.wikipedia.org/wiki/Cucumber_(software)#Steps).
Each *Feature*, *Scenario*, or *Step* should be small and focuses on one thing and encourages many smaller *Features*, *Scenarios* or *Steps*.
Developers will then pull down the *Features*, *Scenarios* or *Steps* via the API and they will code their applications against the expected behavior and uploading the test results. These results can be used for indicating progress and completion.