SpecFlow+ LivingDoc Generator & Rule keyword in Gherkin 6
I'm using the new Rule keyword in my feature file, after an example mapping workshop.
Feature: Train Reservation
Rule: For a train overall, no more than 70% of seats may be reserved in advance
Scenario: No more than 70% of seats may be reserved in advance for a train overall,
Given one coach empty made of 10 seats
When 3 seats are requested
Then the reservation should be assigned these seats "1A, 2A, 3A"
Rule: Ideally no individual coach should have no more than 70% reserved seats
Scenario: Not reserve seats when it exceeds train max capacity 70%
Given 1 coaches of 10 seats and 6 already reserved
When 3 seats are requested
Then the reservation should be failed
Rule: Must put all the seats for one reservation in the same coach
Scenario: Each reservation must be booked in the same coach
Given 2 coaches of 10 seats and 9 seats already reserved in the coach 1
When 2 seats are requested
Then the reservation should be assigned these seats "1B, 2B"
But when I generate a report, the Rule keyword disappeared.
We are aware of this issue and it is on our backlog.
The Rule keyword is known to the syntaxe coloring editor...
Dosen't create error at the execution
But It simply erase everything below it at the report rendering step...
Should I declare a bug?3
Cosials, Benoit no need to create a bug. It's already on our backlog. At the moment I can't say when we are fixing this. AFAIK there was a design meeting already on how to show the rules in LivingDoc in the feature tree on the left.1
Let us know how was your meeting results :)1
My team has also started using the Rule keyword and Living Doc. It would be very handy to see Rules in living doc so that the business can see the tests written for the Rules they have given. Any update on when we might see Rules in Living Doc?2
Is there a backlog item somewhere so that we can monitor it and / or be informed when it is planned or implemented?1
Is there an update on this? The point of specflow is to use gherkin when writing our tests. Is there a work around for those of us which use Visual studio specflow extension?
This would provide us the ability to truly start using specflow and living doc as a way to document source of truth.0
Same for my team: we use the 'Rule' and 'Example' keyword a lot, and it's nicely highlighted in VS 2022 Specflow Extension. But all our scenario are lost once pushed to SpecFlow+ LivingDoc on Azure Devops.
So it would be nice to have an update on this awaited feature planned one year ago.2
Same here: still the same problem. What stack rank does this issue have in the backlog?
But: Thanks for the cool software ... (to not just complain about wha'ts not working, the rest, what works, is really cool)0
Is this keyword supported at this point?
I only ask as it is mentioned in the docs here: https://docs.specflow.org/projects/specflow/en/latest/Gherkin/Gherkin-Reference.html#rule
But, at least for my setup, it never makes it to the livingdoc. It could be I have done something incorrect as the syntax highlighting *is* working in VS2022.
If it's not yet able to be part of the output then perhaps the docs should be updated to state which version of gherkin is recognized or just which keywords are ignored by livingdoc.0
No, it is still not supported in SpecFlow+ LivingDoc.
But it is supported in all other SpecFlow products.0
Glad to hear I'm not doing something wrong.
This makes a change 🙂0
Also hoping to see this implemented in the LivingDoc plugin for Azure DevOps. Thanks!1
I've been waiting for this feature for 2 years now, and I'm not the only one, how can I help you?0
Please sign in to leave a comment.