You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
Am I doing something wrong or this is a bug? I tried a few configurations of Cukedoctor but all resulted in the same output.
The section tags are rendered as scenario tags, while having the following setup:
Feature file that starts as follows
# language: pl
@section-Dinosaurs
@order-10
Funkcja: Praca w trybie offline
Hello,
Thanks.
Yes, I'm trying to use the section layout.
I've compiled and pushed a sample small project here: https://github.com/mpiasta/cukedoctor_sections_test
And I'm attaching a sample PDF output along with adoc that it was generated from. docs.zip
I'm trying to reach a setup where the sections will be moved to top level with given title instead of being nested under Features section:
One more question: is it possible to not render all scenario outline examples in the table of contents as separate pages? (in attached example there are 3 entries that look exactly the same)
Hello,
Am I doing something wrong or this is a bug? I tried a few configurations of Cukedoctor but all resulted in the same output.
The section tags are rendered as scenario tags, while having the following setup:
I end up with something like that - both section naming and ordering seems to be not parsed:
![image](https://user-images.githubusercontent.com/72794167/101909477-d696d900-3bbd-11eb-88f9-13dbdefba486.png)
Swapping language row with section tags (so that they are first thing rendered in the file) freaks cucumber out.
The text was updated successfully, but these errors were encountered: