Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: IDE Support
-
Labels:None
-
Environment:Eclipse
-
Number of attachments :
Description
If a scenario gets reworded, the wording of the Steps class also needs to change. Is there a way to get Eclipse to pick up these changes as refactorings?
(I'm new to JBehave so this may be a rubbish idea, perhaps BAs never decide to reword their scenarios or this feature is already available or scenario writers don't use Eclipse?)
Activity
Mauro Talevi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Summary | Is there a way to sync scenerios with classes? | Is there a way to sync scenarios with classes? |
(is this issue still open? Dec 2009?)
I suggest you rephrase the issue to 'add refactoring support from Steps to stories'. A question is hard to resolve 
Steps to stories? The other way around is more complex since it will require other stories to be refactored too, so that may be a next step.
And no, it is not a rubbish idea. BAs make the same mistakes as developers and testers, refactoring support will only increase the speed for all of us.
The BAs imho SHOULD use the same tools as all others in a project.
Joachim Nilsson
added a comment - (is this issue still open? Dec 2009?)
I suggest you rephrase the issue to 'add refactoring support from Steps to stories'. A question is hard to resolve
Steps to stories? The other way around is more complex since it will require other stories to be refactored too, so that may be a next step.
And no, it is not a rubbish idea. BAs make the same mistakes as developers and testers, refactoring support will only increase the speed for all of us.
The BAs imho SHOULD use the same tools as all others in a project. 
At the moment, the process of keeping in sync the textual scenario and the Steps classes is a manual one.
In the future, the plan is provide more and better integration with IDEs in the editorial/writing stage.