Skip to main content

SpecFlow+ LivingDoc Generator & Rule keyword in Gherkin 6

Comments

14 comments

  • Official comment
    Andreas Willich

    We are aware of this issue and it is on our backlog.

  • Cosials, Benoit

    Same here,

    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
  • Andreas Willich

    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
  • Bruno Boucard

    Sounds good!

    0
  • Cosials, Benoit

    Let us know how was your meeting results :)

    1
  • Robin Hughes

    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
  • damjan cicin-sain

    Is there a backlog item somewhere so that we can monitor it and / or be informed when it is planned or implemented? 

    1
  • Clausing, Kim

    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
  • Samuel Pecoul

    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
  • ckolumbus

    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
  • Richard Cutts

    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
  • Andreas Willich

    No, it is still not supported in SpecFlow+ LivingDoc.

    But it is supported in all other SpecFlow products.

    0
  • Richard Cutts

    Thanks Andreas,
    Glad to hear I'm not doing something wrong.
    This makes a change 🙂

    0
  • Eric Carlson

    Also hoping to see this implemented in the LivingDoc plugin for Azure DevOps. Thanks!

    0

Please sign in to leave a comment.

Powered by Zendesk