Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 3.9.5
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Eclipse luna, Windows and Linux
-
Number of attachments :
Description
When we write scenarios, we use tab character to aline columns of tabulars.
The problem appears when such step is commented (entirely or partially) by prefixing each step line by "!-- ".
The problem comes from the tab characters used in step tabular.
The result is that next uncommented step is recognized pending, and thus scenario fails.
If tab characters are replaced by spaces, the problem disappears.
I set this bug critical and not major because in our case we really need this bugfix.
Activity
For example, these steps work well:
Then in 'Devices' zone, following information is displayed | | DEVICE NAME | WAN INTERFACE | ALLOCATION MODE | | N/A | 'Other' | 'WAN2' | 'DHCP_CLIENT' | When another step
But when first step is commented as
!-- Then in 'Devices' zone, following information is displayed !-- | | DEVICE NAME | WAN INTERFACE | ALLOCATION MODE | !-- | N/A | 'Other' | 'WAN2' | 'DHCP_CLIENT' | When another step
the second step (When another step) is recognized pending, and scenario fails.
The problem comes from tab characters in tabular, wherever the tab character is, at beginning or inside any line.
In above example, tabs are at beginning and inside each lines.
If EVERY tab character is replaced by spaces, the problem disappear.
Eric Klumpp
added a comment - For example, these steps work well:
Then in 'Devices' zone, following information is displayed
| | DEVICE NAME | WAN INTERFACE | ALLOCATION MODE |
| N/A | 'Other' | 'WAN2' | 'DHCP_CLIENT' |
When another step
But when first step is commented as
!-- Then in 'Devices' zone, following information is displayed
!-- | | DEVICE NAME | WAN INTERFACE | ALLOCATION MODE |
!-- | N/A | 'Other' | 'WAN2' | 'DHCP_CLIENT' |
When another step
the second step ( When another step ) is recognized pending, and scenario fails.
The problem comes from tab characters in tabular, wherever the tab character is, at beginning or inside any line.
In above example, tabs are at beginning and inside each lines.
If EVERY tab character is replaced by spaces, the problem disappear. Modify editor settings is only a partial solution for us.
Third parties can add/modify stories, and thus can comment steps like this one.
These third parties are not developpers, don't want to use an IDE, and use their own editor.
The problem is that the resulting effect is not understandable without debug, and these persons don't have time to debug.
These persons will prefer use an other tool.
Thus it prejudices the use of JBehave by third parties and should be corrected.
Eric Klumpp
added a comment - Modify editor settings is only a partial solution for us.
Third parties can add/modify stories, and thus can comment steps like this one.
These third parties are not developpers, don't want to use an IDE, and use their own editor.
The problem is that the resulting effect is not understandable without debug, and these persons don't have time to debug.
These persons will prefer use an other tool.
Thus it prejudices the use of JBehave by third parties and should be corrected. 
Could you please provide some concrete examples?
As a side note, why not simply configure your editor to replace tabs with spaces?