BDD Discovery Tab

Idea ID 2826632

BDD Discovery Tab

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.

example mapping.png


Additional information on Discovery

Essentially, day-to-day BDD activity is a three-step, iterative process:

  1. 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.
  2. Next, document those examples in a way that can be automated, and check for agreement.
  3. Finally, implement the behavior described by each documented example, starting with an automated test to guide the development of the code.
1 Comment
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Waiting for Votes

@Steven T  Thanks a lot for posting this cool idea.
Opening for votes to see if other customers are practicing this.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.