Idea ID 2826632
So we use BDD quite heavily, and as a result have taken to using discovery sessions to identify development requirements, questions and BDD examples upfront allowing for a much smoother process.
What i propose if to allow the output of discovery sessions to be done inside the entity in Octane (Story, Defect and Quality Story) this would allow it to evolve through the meetings and stay with the entity for its life cycle, so an additional tab for Discovery or Additional information in the below format would be amazing.
Additional information on Discovery
Essentially, day-to-day BDD activity is a three-step, iterative process:
- First, take a small upcoming change to the system – a User Story – and talk about concrete examples of the new functionality to explore, discover and agree on the details of what’s expected to be done.
- Next, document those examples in a way that can be automated, and check for agreement.
- Finally, implement the behavior described by each documented example, starting with an automated test to guide the development of the code.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.