Ok, I will raise an Jira issue because of the execution depending on
outcome.
Concerning pending steps: It looks the same in the report when no step is
found and when a matching step method has been marked @Pending. But this is
not the same situation to me but the same word is used.
Wouldn't it b
A step that is not found (or whose signature is not matched which is the same)
is considered pending. You can think pending as synonymous to not found.
Passing nulls around is not a safe nor good practice as it simply shifts the
problem without solving it. You can activate the step monitor to
I tried the new lifecylce steps in JBehave 4 beta-6.
I wondered why my lifecycle after step was not executed (pending state).
It was because the step method used a argument although the step name does
not contain a parameter:
@Given("the user logs out")
*public* *void* logout(String *user*) {}
