Details
Improvement
Resolved
Major
Description
In some languages, e.g. Italian, Portuguese and Spanish, the "And" keyword is translated as a single letter ("E" or "Y") which makes it possible to find in some textual acronym. If the acronym ends in that letter, the parser will consider it a new step.
A comprehensive solution would be to require that RegexStoryParser identifies the second occurrence of a keyword in scenario text only if preceded by a newline.
This solution would also allow users to easily comment out steps prefixing the starting work (on same line with !-- keyword)
Activity
Mauro Talevi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
In some languages, e.g. Italian, Portuguese and Spanish, the "And" keyword is translated as a single letter ("E" or "Y") which makes it possible to find in some textual acronym. If the acronym ends in that letter, the parser will consider it a new step.
A comprehensive solution would be to require that all steps, i.e. all starting keywords, are preceded by a newline. This solution would also allow users to easily comment out steps prefixing the starting work (on same line with !-- keyword) |
In some languages, e.g. Italian, Portuguese and Spanish, the "And" keyword is translated as a single letter ("E" or "Y") which makes it possible to find in some textual acronym. If the acronym ends in that letter, the parser will consider it a new step.
A comprehensive solution would be to require that RegexStoryParser identifies the second occurrence of a keyword in scenario text only if preceded by a newline. This solution would also allow users to easily comment out steps prefixing the starting work (on same line with !-- keyword) |
Mauro Talevi
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Hi Mauro,
I think this is a good solution, and also will allow us to use keywords inside a Example table.