Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Priority not taken into account when detecting duplicate steps.

Description

In the past (version 5.0) of JBehave the same step could be present twice as long as it had a different priority assigned to it (the default is 0).

 

Since 5.1 (also in 5.1.1) the following exception is thrown when the same step is present twice with a different priority (link to documentation of feature: ) :

 

Activity

Show:

Valery Yatsynovich August 21, 2023 at 9:12 AM

ok, I got you point, then my question is: why do you need other steps with lower priorities? they won’t be used at all

Gunther Schrijvers August 21, 2023 at 9:02 AM

Indeed in versions prior to 5.1.1 the one with the highest priority would be selected.

Valery Yatsynovich July 21, 2023 at 11:57 AM

the following exception is thrown when the same step is present twice with a different priority

could you please elaborate more on this? From my understanding: if several steps with the same syntax, but different priorities are presented, then prior 5.1.1 (where exception is thrown) only one step with the highest priority is always used, while other are not used at all. Am I correct? Or do you have some business case around this?

Details

Assignee

Reporter

Priority

Created June 16, 2023 at 7:21 AM
Updated August 21, 2023 at 9:12 AM
Configure