Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Structure View does not support Lifecycle steps #72

Open
cse-garylo opened this issue Apr 28, 2022 · 1 comment
Open

Structure View does not support Lifecycle steps #72

cse-garylo opened this issue Apr 28, 2022 · 1 comment

Comments

@cse-garylo
Copy link

cse-garylo commented Apr 28, 2022

Applies to plugin v1.57

My story has Lifecycle steps but I do not see them appear in the Structure View

image

I would expect if a story has Lifecycle steps, they would show up in the Structure View accordingly to their Scope.

ex:
Lifecycle:
Before:
Scope: STORY
[steps to be executed before each story]
Scope: SCENARIO
[steps to be executed before each scenario]
Scope: STEP
[steps to be executed before each scenario step]
After:
Scope: STEP
[steps to be executed after each scenario step]
Scope: SCENARIO
[steps to be executed after each scenario]
Scope: STORY
[steps to be executed after each story]

Should display in Structure tree view as:

filename
 V Story
  V Before Story Steps
  V Scenario1
   V Before Scenario Steps
   V Before Each Scenario Step Steps
   Scenario1 Step1
   V After Each Scenario Step Steps
   ...
   V After Scenario Steps
  V Scenario2
   V Before Scenario Steps
   V Before Each Scenario Step Steps
   Scenario1 Step2
   V After Each Scenario Step Steps
   ...
   V After Scenario Steps
  V After Story Steps
  V Examples:
@picimako
Copy link
Collaborator

picimako commented May 5, 2022

Hi @cse-garylo ,

Originally I wanted to include Lifecycles as well, but they are not supported (properly) by the implementation of the JBehave language support, so I excluded them for now.

When I'll have some time to work on this plugin again I'll check if the language support can be extended (or worked around) somehow, but I can't say anything certain at the moment. Until then I'll add a note in the readme about this limitation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants