[
https://jira.codehaus.org/browse/JBEHAVE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289131#comment-289131
]
Arnauld Loyer edited comment on JBEHAVE-233 at 1/23/12 4:54 AM:
----------------------------------------------------------------
As author of https://github.com/Arnauld/jbehave-eclipse-plugin, here are some
updates:
+ Syntax coloring (partially implemented: only narratives, scenario, steps and
parameters)
+ Completion has been fixed and improved to work even with parameters partially
typed (https://github.com/Arnauld/jbehave-eclipse-plugin/issues/7 and
https://github.com/Arnauld/jbehave-eclipse-plugin/issues/4)
+ Outline is partially done (only quick outline for now but outline view will
come soon https://github.com/Arnauld/jbehave-eclipse-plugin/issues/22)
+ Quick search feature allow to efficiently search and insert steps while
keeping your fingers on keyboard and writing stories
+ Support the "in-trunk" step variants feature
(https://github.com/Arnauld/jbehave-eclipse-plugin/pull/18)
+ Jump to declaration ("support for opening declarations of steps from the
scenario files")
I have added the following in the issue list:
+ support for finding usages of steps in scenario files from the declaration
+ refactoring support: when editing the annotations, scenarios using the step
get rewritten
Feel free to add more suggestions as Gabriel did.
I would probably requires some help for this one:
+ support for opening the declaration of failed steps when running junit
since it would requires an alternate JUnitStories that provides more fine
grained tests. Actually the runner create a single test with all stories. It
would be nice to dynamically generate one suite per story, in which each step
would be a testcase by itself. I'm not yet enough familiar with Junit 4 runner
and new suite management. My concerns are about the sharing of the Embedder
between the different suite, and the split of a single story into sub-tests.
was (Author: technbolts):
As author of https://github.com/Arnauld/jbehave-eclipse-plugin, here are
some updates:
+ Syntax coloring (partially implemented: only narratives, scenario, steps and
parameters)
+ Completion has been fixed and improved to work even with parameters partially
typed (https://github.com/Arnauld/jbehave-eclipse-plugin/issues/7 and
https://github.com/Arnauld/jbehave-eclipse-plugin/issues/4)
+ Outline is partially done (only quick outline for now but outline view will
come soon https://github.com/Arnauld/jbehave-eclipse-plugin/issues/22)
+ Quick search feature allow to efficiently search and insert steps while
keeping your fingers on keyboard and writing stories
+ Support the "in-trunk" step variants feature
(https://github.com/Arnauld/jbehave-eclipse-plugin/pull/18)
+ Jump to declaration ("support for opening declarations of steps from the
scenario files")
I have added the following in the issue list:
+ support for finding usages of steps in scenario files from the declaration
+ refactoring support: when editing the annotations, scenarios using the step
get rewritten
Feel free to add more suggestions as Gabriel did.
I would probably requires some help for this one:
+ support for opening the declaration of failed steps when running junit
since it would requires an alternate JUnitStories that provides more fine
grained tests: probably by dynamically generate one suite per story, in which
each step would be a testcase by itself. I'm not yet enough familiar with Junit
4 runner and new suite management.
> Eclipse plugin for navigating between textual and code steps
> ------------------------------------------------------------
>
> Key: JBEHAVE-233
> URL: https://jira.codehaus.org/browse/JBEHAVE-233
> Project: JBehave
> Issue Type: New Feature
> Reporter: Jonathan Ross
>
> As an avid user of jBehave, I find maintaining steps very laborious, so I
> would like an eclipse plugin with:
> * support for opening declarations of steps from the scenario files
> * support for finding usages of steps in scenario files from the declaration
> * support for opening the declaration of failed steps when running junit
> Nice to have:
> * refactoring support: when editing the annotations, scenarios using the step
> get rewritten
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
