[jbehave-dev] [jira] Created: (JBEHAVE-329) Add @Inherited annotation to control inheritance behaviour of annotated configuration
Add @Inherited annotation to control inheritance behaviour of annotated configuration - Key: JBEHAVE-329 URL: http://jira.codehaus.org/browse/JBEHAVE-329 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Fix For: 3.0 As explained in JBEHAVE-327, it's useful to control inheritance behaviour. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-327) Remove dependency on javassist by using standard JDK annotation functionality
[ http://jira.codehaus.org/browse/JBEHAVE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-327. -- Resolution: Fixed Resolving this issue, as the dependency on javassist as been removed. Inheritance issue now tracked by JBEHAVE-329. Remove dependency on javassist by using standard JDK annotation functionality - Key: JBEHAVE-327 URL: http://jira.codehaus.org/browse/JBEHAVE-327 Project: JBehave Issue Type: Improvement Components: Core Reporter: Brian Repko Assignee: Mauro Talevi Fix For: 3.0 Attachments: 0001-removal-of-javassist.patch, 0002-merge-change-of-Exception-type.patch, 0003-add-support-for-inherited-annotation-values.patch, AnnotationFinder.java Use of javassist is typically done for access to non-RUNTIME Retention annotations or for annotation parsing over a large set of classes when you don't want to load the class. We don't have those use cases and thus can eliminate the javassist dependency in AnnotationFinder. New version of AnnotationFinder is attached that seems to work - I wasn't sure if getAnnotation should look at interfaces and/or superclasses (not needed if we appropriate add the @Inherited to our annotations). jbehave-core/pom.xml also changed to remove the dependency. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-324) Add methods in EmbedderMonitor to distinguish running an Embeddable from running a story as path
[ http://jira.codehaus.org/browse/JBEHAVE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-324. -- Resolution: Fixed Add methods in EmbedderMonitor to distinguish running an Embeddable from running a story as path Key: JBEHAVE-324 URL: http://jira.codehaus.org/browse/JBEHAVE-324 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-329) Add inherit* property for array-valued annotation property to control inheritance behaviour
[ http://jira.codehaus.org/browse/JBEHAVE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-329: - Description: As explained in JBEHAVE-327, it's useful to control inheritance behaviour. By default inheritance behaviour is true, meaning AnnotationFinder goes up the inheritance tree and collects array values for a given annotation property. This inheritance behaviour can be inhibited by setting the property inheritpropertyName=false was:As explained in JBEHAVE-327, it's useful to control inheritance behaviour. Summary: Add inherit* property for array-valued annotation property to control inheritance behaviour (was: Add @Inherited annotation to control inheritance behaviour of annotated configuration) Add inherit* property for array-valued annotation property to control inheritance behaviour --- Key: JBEHAVE-329 URL: http://jira.codehaus.org/browse/JBEHAVE-329 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Fix For: 3.0 As explained in JBEHAVE-327, it's useful to control inheritance behaviour. By default inheritance behaviour is true, meaning AnnotationFinder goes up the inheritance tree and collects array values for a given annotation property. This inheritance behaviour can be inhibited by setting the property inheritpropertyName=false -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-329) Add inherit* property for array-valued annotation property to control inheritance behaviour
[ http://jira.codehaus.org/browse/JBEHAVE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-329. -- Resolution: Fixed Applied solution 3a) as proposed. Add inherit* property for array-valued annotation property to control inheritance behaviour --- Key: JBEHAVE-329 URL: http://jira.codehaus.org/browse/JBEHAVE-329 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Fix For: 3.0 As explained in JBEHAVE-327, it's useful to control inheritance behaviour. By default inheritance behaviour is true, meaning AnnotationFinder goes up the inheritance tree and collects array values for a given annotation property. This inheritance behaviour can be inhibited by setting the property inheritpropertyName=false -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-330) Allow pluggable strategy to resolve file paths from story location
Allow pluggable strategy to resolve file paths from story location -- Key: JBEHAVE-330 URL: http://jira.codehaus.org/browse/JBEHAVE-330 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.0 FilePrintStreamFactory should allow a pluggable strategy to resolve file paths for directory and name of files for each story location. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Commented: (JBEHAVE-312) Configuration option for non-greedy matchers for steps
[
http://jira.codehaus.org/browse/JBEHAVE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=232636#action_232636
]
Mauro Talevi commented on JBEHAVE-312:
--
The prioritisation strategy is now configurable in 3.x:
http://jbehave.org/reference/latest/prioritising-steps.html
Configuration option for non-greedy matchers for steps
--
Key: JBEHAVE-312
URL: http://jira.codehaus.org/browse/JBEHAVE-312
Project: JBehave
Issue Type: Improvement
Components: Core
Affects Versions: 2.5
Reporter: James Ravn
The biggest sore point for my team are the greedy reg-ex matchers for step
prose.
This was somewhat solved in another ticket which added a {{priority}} field
to the annotation.
However, this does not scale well with a large amount of steps. It's
unmanageable, and a bit ugly, to have to worry about a global priority number.
This problem would be best fixed if the reg-ex matcher was simply non-greedy.
A usable solution, I think, would be to provide a configuration option in the
StepsConfiguration to enable this.
(On a side note, you may want to consider moving to a feature rich templating
language like velocity).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-332) Refactor NumberConverter to use injectable NumberFormat
Refactor NumberConverter to use injectable NumberFormat --- Key: JBEHAVE-332 URL: http://jira.codehaus.org/browse/JBEHAVE-332 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.0 Refactor NumberConverter to parse numbers using injectable NumberFormat, instead of Number classes' valueOf() methods. Locale-specific formats are supported via NumberFormat.getInstance(Locale), while defaulting to NumberFormat.getInstance(). Also refactor NumberListConverter to use NumberConverter with provided NumberFormat, again defaulting to NumberFormat.getInstance(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-332) Refactor NumberConverter to use injectable NumberFormat
[ http://jira.codehaus.org/browse/JBEHAVE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-332. -- Resolution: Fixed Refactor NumberConverter to use injectable NumberFormat --- Key: JBEHAVE-332 URL: http://jira.codehaus.org/browse/JBEHAVE-332 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.0 Refactor NumberConverter to parse numbers using injectable NumberFormat, instead of Number classes' valueOf() methods. Locale-specific formats are supported via NumberFormat.getInstance(Locale), while defaulting to NumberFormat.getInstance(). Also refactor NumberListConverter to use NumberConverter with provided NumberFormat, again defaulting to NumberFormat.getInstance(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-333) Cannot use '?' character in step annotations, escaping in regex is not happening properly.
[ http://jira.codehaus.org/browse/JBEHAVE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-333: - Summary: Cannot use '?' character in step annotations, escaping in regex is not happening properly. (was: Cannot use ? in @Given() annotations, escaping in Regex is not happening properly.) Cannot use '?' character in step annotations, escaping in regex is not happening properly. -- Key: JBEHAVE-333 URL: http://jira.codehaus.org/browse/JBEHAVE-333 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.0 Reporter: Paul Hammant Priority: Minor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Commented: (JBEHAVE-331) Allow Step-level dependencies
[ http://jira.codehaus.org/browse/JBEHAVE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=233111#action_233111 ] Mauro Talevi commented on JBEHAVE-331: -- Yes, agreed, we need to continue the discussion as the scope of the proposed functionality is not yet defined. We already have Scenario templates supported in JBehave, and it does not sound to me like this is what Victor was after. Some form of allowing definition of macro-steps or transitive step dependencies is closer to the mark, IMO. Allow Step-level dependencies - Key: JBEHAVE-331 URL: http://jira.codehaus.org/browse/JBEHAVE-331 Project: JBehave Issue Type: New Feature Environment: n/a Reporter: Victor Moura Currently JBehave does not support Step-Level Dependencies. It may be useful to enable this feature so that steps can be created referencing directly other steps. The functionality was suggested in the following thread on the user list. http://www.mail-archive.com/u...@jbehave.codehaus.org/msg00494.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Reopened: (JBEHAVE-251) Selenium (under JBehave control) needs to be able to be instansiable at Story as well as Scenario level
[ http://jira.codehaus.org/browse/JBEHAVE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-251: -- Assignee: Mauro Talevi (was: Paul Hammant) Issues should not be closed, but resolved. Selenium (under JBehave control) needs to be able to be instansiable at Story as well as Scenario level --- Key: JBEHAVE-251 URL: http://jira.codehaus.org/browse/JBEHAVE-251 Project: JBehave Issue Type: Improvement Affects Versions: web-2.1.6 Reporter: Paul Hammant Assignee: Mauro Talevi Fix For: web-3.0 Fixed in CL 1599 - SeleniumSteps is deprecated SeleniumStorySteps and SeleniumScenarioSteps are new -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-251) Selenium (under JBehave control) needs to be able to be instansiable at Story as well as Scenario level
[ http://jira.codehaus.org/browse/JBEHAVE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-251. -- Resolution: Fixed Selenium (under JBehave control) needs to be able to be instansiable at Story as well as Scenario level --- Key: JBEHAVE-251 URL: http://jira.codehaus.org/browse/JBEHAVE-251 Project: JBehave Issue Type: Improvement Affects Versions: web-2.1.6 Reporter: Paul Hammant Assignee: Mauro Talevi Fix For: web-3.0 Fixed in CL 1599 - SeleniumSteps is deprecated SeleniumStorySteps and SeleniumScenarioSteps are new -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-220) Allow per-story and per-scenario meta-information
[ http://jira.codehaus.org/browse/JBEHAVE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-220: - Priority: Major (was: Minor) Assignee: Mauro Talevi Issue Type: New Feature (was: Improvement) Summary: Allow per-story and per-scenario meta-information (was: Allow per-scenario meta-information) Allow per-story and per-scenario meta-information - Key: JBEHAVE-220 URL: http://jira.codehaus.org/browse/JBEHAVE-220 Project: JBehave Issue Type: New Feature Components: Core Reporter: Chris Jensen Assignee: Mauro Talevi Fix For: 3.1 From a development management perspective, BDD could be extremely useful in helping to track and understand who is creating specifications and when they are being injected. Since requirements like this will vary between users, it would be a good idea to implement as generically as possible and then provide an example or reference. My thoughts on what would be useful in my own situation: - A way to indicate the Author(s) of a scenario - A way to indicate the Owner of a story - A way to indicate the Creation Date of a scenario - A way to indicate the Last Update Date of a scenario - The injection phase of the scenario (eg. grooming, planning, development...) I don't think these should be included in the grammar as individual, specific elements, but perhaps the grammar could have a syntax for optional meta-information. The grammar would allow a word (eg. Meta:) followed by a category, perhaps emphasized with a symbol (eg. @Author) and then followed by any arbitrary text. This would allow interesting things... Meta: @Author John Meta: @Role Product Owner Meta: @Created 2009-11-08 Meta: @Injection Backlog Grooming -OR- Meta: @Author Fred Meta: @Role Quality Engineer Meta: @Created 2009-12-02 Meta: @Injection Sprint Planning -OR- Meta: @Author Colin Meta: @Role Developer Meta: @Created 2009-12-10 Meta: @Injection Development Being able to say that, for instance, only 20% of scenarios are created in backlog grooming, while another 20% are created in sprint planning and 60% are created during development would be very useful in identifying and resolving process impediments and training product owners and teams to define requirements earlier so they don't run into velocity impacts when they are discovered late in a sprint. Allowing meta-data would enable scenario management tool development. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-234) Improve JUnit integration
[ http://jira.codehaus.org/browse/JBEHAVE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-234: - Component/s: Core Improve JUnit integration - Key: JBEHAVE-234 URL: http://jira.codehaus.org/browse/JBEHAVE-234 Project: JBehave Issue Type: Improvement Components: Core Reporter: Jonathan Ross Fix For: 3.1 As a developer using jBehave running in JUnit in Eclipse, I would like to easily determine 1. how many individual scenarios have passed or failed, and 2. which steps failures occur in What springs to mind, is to wire each scenario up as separate JUnit TestCase (rather than the single 'testScenario()' method). Doing so, I would easily be able to drill down to the individually failing scenarios more easily. Regarding finding out which step failed, short of writing a fully-fledged plug-in, this would be a simple matter of retaining the actual failure exception and setting this in JUnit's test result - the failed step should be in the stack trace reported by JUnit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-335) Migrate to Wicket as web application framework
Migrate to Wicket as web application framework -- Key: JBEHAVE-335 URL: http://jira.codehaus.org/browse/JBEHAVE-335 Project: JBehave Issue Type: New Feature Components: Web Runner Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.0 Wicket shares the same philosophy as Waffle (embeddable, pure Java, no XML) and has a wide community support. Users would extend a Wicket Application class to specify configuration and steps instances, similarly to what done with Waffle Registrar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Work started: (JBEHAVE-335) Refactor Web Runner to use Wicket as web application framework
[ http://jira.codehaus.org/browse/JBEHAVE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-335 started by Mauro Talevi. Refactor Web Runner to use Wicket as web application framework -- Key: JBEHAVE-335 URL: http://jira.codehaus.org/browse/JBEHAVE-335 Project: JBehave Issue Type: New Feature Components: Web Runner Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.0 Wicket shares the same philosophy as Waffle (embeddable, pure Java, no XML) and has a wide community support. From users' point of view the only change would be extend a Wicket Application class to specify configuration and steps instances, instead of a Waffle Registrar. A doc page should help in migrating from Registrar to Application class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-335) Refactor Web Runner to use Wicket as web application framework
[ http://jira.codehaus.org/browse/JBEHAVE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-335: - Description: Wicket shares the same philosophy as Waffle (embeddable, pure Java, no XML) and has a wide community support. From users' point of view the only change would be extend a Wicket Application class to specify configuration and steps instances, instead of a Waffle Registrar. A doc page should help in migrating from Registrar to Application class. was: Wicket shares the same philosophy as Waffle (embeddable, pure Java, no XML) and has a wide community support. Users would extend a Wicket Application class to specify configuration and steps instances, similarly to what done with Waffle Registrar. Summary: Refactor Web Runner to use Wicket as web application framework (was: Migrate to Wicket as web application framework) Refactor Web Runner to use Wicket as web application framework -- Key: JBEHAVE-335 URL: http://jira.codehaus.org/browse/JBEHAVE-335 Project: JBehave Issue Type: New Feature Components: Web Runner Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.0 Wicket shares the same philosophy as Waffle (embeddable, pure Java, no XML) and has a wide community support. From users' point of view the only change would be extend a Wicket Application class to specify configuration and steps instances, instead of a Waffle Registrar. A doc page should help in migrating from Registrar to Application class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-213) Scenario runner form submission should support both GET and POST methods
[ http://jira.codehaus.org/browse/JBEHAVE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-213: - Fix Version/s: (was: web-3.0) Scenario runner form submission should support both GET and POST methods -- Key: JBEHAVE-213 URL: http://jira.codehaus.org/browse/JBEHAVE-213 Project: JBehave Issue Type: Improvement Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-2.1.6 POST is required for executing very long scenarios - and is now the default. Can be changed via the drop-down selection next to the Run Scenario link. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-192) Allow both relative and full path views for file contents
[ http://jira.codehaus.org/browse/JBEHAVE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-192: - Fix Version/s: (was: web-3.0) Allow both relative and full path views for file contents - Key: JBEHAVE-192 URL: http://jira.codehaus.org/browse/JBEHAVE-192 Project: JBehave Issue Type: Improvement Affects Versions: web-2.1.2 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-2.1.3 Useful when the relative path view may fail for some reason. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Assigned: (JBEHAVE-188) Allow viewing of unarchived file contents
[ http://jira.codehaus.org/browse/JBEHAVE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-188: Assignee: Mauro Talevi Allow viewing of unarchived file contents - Key: JBEHAVE-188 URL: http://jira.codehaus.org/browse/JBEHAVE-188 Project: JBehave Issue Type: New Feature Components: Web Runner Affects Versions: web-2.1 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-2.1.1, web-3.0 Currently, the archive content can be listed as file paths. In some case, it may be useful to view the actual contents of the unarchived files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Commented: (JBEHAVE-335) Refactor Web Runner to use Wicket as web application framework
[ http://jira.codehaus.org/browse/JBEHAVE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235205#action_235205 ] Mauro Talevi commented on JBEHAVE-335: -- Brian, Wicket is not a pure MVC framework, but more a component-oriented one. It plays very nice with Java and rich-client features are easier than in other action-based frameworks. Other factors influencing the choice of framework are the community base and the documentation, both of which are very wide for Wicket. Refactor Web Runner to use Wicket as web application framework -- Key: JBEHAVE-335 URL: http://jira.codehaus.org/browse/JBEHAVE-335 Project: JBehave Issue Type: New Feature Components: Web Runner Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.0 Wicket shares the same philosophy as Waffle (embeddable, pure Java, no XML) and has a wide community support. From users' point of view the only change would be extend a Wicket Application class to specify configuration and steps instances, instead of a Waffle Registrar. A doc page should help in migrating from Registrar to Application class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-336) Find Steps page
Find Steps page --- Key: JBEHAVE-336 URL: http://jira.codehaus.org/browse/JBEHAVE-336 Project: JBehave Issue Type: New Feature Components: Web Runner Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.0 Use JBehave Core's StepFinder to allow a simple textarea to cut paste a textual step and to find the matching step patterns and (optionally) show the corresponding methods in the steps instance. It should also show the list of steps instances configured in the application amongst which the steps are searched. If no textual step is provided, all patterns available should be shown. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Commented: (JBEHAVE-337) jbehave-maven-plugin thows NoClassDefFoundError org/apache/log4j/Priority when maven project includes log4j dependency
[ http://jira.codehaus.org/browse/JBEHAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235499#action_235499 ] Mauro Talevi commented on JBEHAVE-337: -- Add dependency to plugin rather than the project (see example below) and it will be picked up. This is a Maven classloading issue that is independent of the JBehave plugin. We'll update the documentation to reflect this common use case. plugin groupIdorg.jbehave/groupId artifactIdjbehave-maven-plugin/artifactId dependencies dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.16/version /dependency /dependencies /plugin jbehave-maven-plugin thows NoClassDefFoundError org/apache/log4j/Priority when maven project includes log4j dependency -- Key: JBEHAVE-337 URL: http://jira.codehaus.org/browse/JBEHAVE-337 Project: JBehave Issue Type: Bug Components: Maven Plugin Affects Versions: 3.0 Environment: Ubuntu 10.4, sun java 1.6.0_20-b02, maven 2.2.1 Reporter: Jonathan Choate Attachments: log4j-error.tar.gz If my pom.xml contains a dependency on log4j then when I run the target mvn integration-test I get a stack trace indicating that the jbehave-maven-plugin can't find the log4j classes. I've attached a trivial maven project that reproduces the issue. I do not see this issue when I run the tests in eclipse as junit tests and the tests run fine if I remove log4j. The following is the complete stack trace: java.lang.NoClassDefFoundError: org/apache/log4j/Priority at freemarker.log.Log4JLoggerFactory.getLogger(Log4JLoggerFactory.java:65) at freemarker.log.Logger.getLogger(Logger.java:255) at freemarker.template.utility.SecurityUtilities.clinit(SecurityUtilities.java:67) at freemarker.ext.beans.BeansWrapper.clinit(BeansWrapper.java:147) at freemarker.template.ObjectWrapper.clinit(ObjectWrapper.java:69) at freemarker.core.Configurable.init(Configurable.java:132) at freemarker.template.Configuration.init(Configuration.java:109) at freemarker.template.Configuration.clinit(Configuration.java:96) at org.jbehave.core.reporters.FreemarkerViewGenerator.configure(FreemarkerViewGenerator.java:208) at org.jbehave.core.reporters.FreemarkerViewGenerator.init(FreemarkerViewGenerator.java:60) at org.jbehave.core.configuration.Configuration.init(Configuration.java:159) at org.jbehave.core.configuration.MostUsefulConfiguration.init(MostUsefulConfiguration.java:49) at org.jbehave.core.embedder.Embedder.init(Embedder.java:30) at org.jbehave.core.embedder.Embedder.init(Embedder.java:37) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.jbehave.core.embedder.EmbedderClassLoader.newInstance(EmbedderClassLoader.java:37) at org.jbehave.mojo.AbstractEmbedderMojo.newEmbedder(AbstractEmbedderMojo.java:228) at org.jbehave.mojo.RunStoriesAsEmbeddables.execute(RunStoriesAsEmbeddables.java:15) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
[jbehave-dev] [jira] Commented: (JBEHAVE-338) Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3
[ http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235534#action_235534 ] Mauro Talevi commented on JBEHAVE-338: -- Brian is quite right - this is not a regression, rather a feature (JBEHAVE-325). It is also documented in http://jbehave.org/reference/stable/migrating-from-2.x.html The usecase of indented scenarios is quite rare and is outweighted by the advantage of allowing keyword in comments, titles, tables etc ... If one wants to keep at all costs tabs/spaces before keywords, a possible workaround would be writing a pre-parser that strips these tabs/spaces before passing it to the RegexStoryParser. Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3 - Key: JBEHAVE-338 URL: http://jira.codehaus.org/browse/JBEHAVE-338 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.0 Environment: Windows Reporter: Paul Hammant Priority: Minor A client had indented JB scenarios (tabs and/or spaces) in the .scenario files. When upgraded to JB3, and everything else was working for the renamed .story files. the scenarios were not being executed. It seems regex made no match. We had breakpoints in place so we could see the BeforeScenario being invoked, but none of the steps. When we removed the left-whitespace, it worked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-339) HTML report numbers could be more tabular
[ http://jira.codehaus.org/browse/JBEHAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-339: - Description: guice.stories.simple_guice_example Scenarios: 1 (Failed: 0) Steps: 3 (Successful: 3; Pending: 0; Not Performed: 0; Failed: 0; Ignorable: 0) i18n.stories.fr_trader_is_alerted_of_status Scenarios: 1 (Failed: 0) Steps: 13 (Successful: 0; Pending: 4; Not Performed: 9; Failed: 0; Ignorable: 0) i18n.stories.it_trader_is_alerted_of_status Scenarios: 2 (Failed: 0) Steps: 15 (Successful: 7; Pending: 8; Not Performed: 0; Failed: 0; Ignorable: 0) The output formats as a string. There are some numbers is parens. These should really be tdnumbers/td There should also be totals at the bottom of the set, and column headings at the top :) was: guice.stories.simple_guice_example Scenarios: 1 (Failed: 0) Steps: 3 (Successful: 3; Pending: 0; Not Performed: 0; Failed: 0; Ignorable: 0;) i18n.stories.fr_trader_is_alerted_of_status Scenarios: 1 (Failed: 0) Steps: 13 (Successful: 0; Pending: 4; Not Performed: 9; Failed: 0; Ignorable: 0;) i18n.stories.it_trader_is_alerted_of_status Scenarios: 2 (Failed: 0) Steps: 15 (Successful: 7; Pending: 8; Not Performed: 0; Failed: 0; Ignorable: 0;) The output formats as a string. There are some numbers is parens. These should really be tdnumbers/td There should also be totals at the bottom of the set, and column headings at the top :) HTML report numbers could be more tabular -- Key: JBEHAVE-339 URL: http://jira.codehaus.org/browse/JBEHAVE-339 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.0 Reporter: Paul Hammant guice.stories.simple_guice_exampleScenarios: 1 (Failed: 0) Steps: 3 (Successful: 3; Pending: 0; Not Performed: 0; Failed: 0; Ignorable: 0) i18n.stories.fr_trader_is_alerted_of_status Scenarios: 1 (Failed: 0) Steps: 13 (Successful: 0; Pending: 4; Not Performed: 9; Failed: 0; Ignorable: 0) i18n.stories.it_trader_is_alerted_of_status Scenarios: 2 (Failed: 0) Steps: 15 (Successful: 7; Pending: 8; Not Performed: 0; Failed: 0; Ignorable: 0) The output formats as a string. There are some numbers is parens. These should really be tdnumbers/td There should also be totals at the bottom of the set, and column headings at the top :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-337) Document how to configure jbehave-maven-plugin to be aware of log4j dependency
[ http://jira.codehaus.org/browse/JBEHAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-337: - Fix Version/s: 3.1 Issue Type: Task (was: Bug) Summary: Document how to configure jbehave-maven-plugin to be aware of log4j dependency (was: jbehave-maven-plugin thows NoClassDefFoundError org/apache/log4j/Priority when maven project includes log4j dependency) Document how to configure jbehave-maven-plugin to be aware of log4j dependency -- Key: JBEHAVE-337 URL: http://jira.codehaus.org/browse/JBEHAVE-337 Project: JBehave Issue Type: Task Components: Maven Plugin Affects Versions: 3.0 Environment: Ubuntu 10.4, sun java 1.6.0_20-b02, maven 2.2.1 Reporter: Jonathan Choate Fix For: 3.1 Attachments: log4j-error.tar.gz If my pom.xml contains a dependency on log4j then when I run the target mvn integration-test I get a stack trace indicating that the jbehave-maven-plugin can't find the log4j classes. I've attached a trivial maven project that reproduces the issue. I do not see this issue when I run the tests in eclipse as junit tests and the tests run fine if I remove log4j. The following is the complete stack trace: java.lang.NoClassDefFoundError: org/apache/log4j/Priority at freemarker.log.Log4JLoggerFactory.getLogger(Log4JLoggerFactory.java:65) at freemarker.log.Logger.getLogger(Logger.java:255) at freemarker.template.utility.SecurityUtilities.clinit(SecurityUtilities.java:67) at freemarker.ext.beans.BeansWrapper.clinit(BeansWrapper.java:147) at freemarker.template.ObjectWrapper.clinit(ObjectWrapper.java:69) at freemarker.core.Configurable.init(Configurable.java:132) at freemarker.template.Configuration.init(Configuration.java:109) at freemarker.template.Configuration.clinit(Configuration.java:96) at org.jbehave.core.reporters.FreemarkerViewGenerator.configure(FreemarkerViewGenerator.java:208) at org.jbehave.core.reporters.FreemarkerViewGenerator.init(FreemarkerViewGenerator.java:60) at org.jbehave.core.configuration.Configuration.init(Configuration.java:159) at org.jbehave.core.configuration.MostUsefulConfiguration.init(MostUsefulConfiguration.java:49) at org.jbehave.core.embedder.Embedder.init(Embedder.java:30) at org.jbehave.core.embedder.Embedder.init(Embedder.java:37) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.jbehave.core.embedder.EmbedderClassLoader.newInstance(EmbedderClassLoader.java:37) at org.jbehave.mojo.AbstractEmbedderMojo.newEmbedder(AbstractEmbedderMojo.java:228) at org.jbehave.mojo.RunStoriesAsEmbeddables.execute(RunStoriesAsEmbeddables.java:15) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at
[jbehave-dev] [jira] Commented: (JBEHAVE-338) Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3
[ http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235544#action_235544 ] Mauro Talevi commented on JBEHAVE-338: -- Yes, it's essentially the pre-parsing concept proposed above. But it's probably best done in a decorator class as it's a rather rare corner case to justify it being done by default (would slow down parsing that is already not lighting fast). Anybody wanting to use indentation could simply configure the decorator around the regex story parser. Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3 - Key: JBEHAVE-338 URL: http://jira.codehaus.org/browse/JBEHAVE-338 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.0 Environment: Windows Reporter: Paul Hammant Priority: Minor A client had indented JB scenarios (tabs and/or spaces) in the .scenario files. When upgraded to JB3, and everything else was working for the renamed .story files. the scenarios were not being executed. It seems regex made no match. We had breakpoints in place so we could see the BeforeScenario being invoked, but none of the steps. When we removed the left-whitespace, it worked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-340) Upgrade default dependency to Selenium 2 - backward compatible with Selenium 1
[
http://jira.codehaus.org/browse/JBEHAVE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-340.
--
Resolution: Fixed
Upgrade default dependency to Selenium 2 - backward compatible with Selenium 1
--
Key: JBEHAVE-340
URL: http://jira.codehaus.org/browse/JBEHAVE-340
Project: JBehave
Issue Type: Task
Components: Web Selenium
Reporter: Mauro Talevi
Priority: Minor
Fix For: web-3.0
As Selenium 2 is drop-in backward compatible with Selenium 1, having the
default dependency on the latest release of Selenium 2 is useful as it can
help gradual migration from Selenium to WebDriver.
Users not wanting Selenium 2 in the classpath when using jbehave-web-selenium
can simply exclude the dependency
{code:xml}
dependency
groupIdorg.seleniumhq.selenium/groupId
artifactIdselenium/artifactId
/dependency
{code:xml}
and replace with the Selenium 1 dependency.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-340) Upgrade default dependency to Selenium 2 - backward compatible with Selenium 1
Upgrade default dependency to Selenium 2 - backward compatible with Selenium 1
--
Key: JBEHAVE-340
URL: http://jira.codehaus.org/browse/JBEHAVE-340
Project: JBehave
Issue Type: Task
Components: Web Selenium
Reporter: Mauro Talevi
Priority: Minor
Fix For: web-3.0
As Selenium 2 is drop-in backward compatible with Selenium 1, having the
default dependency on the latest release of Selenium 2 is useful as it can help
gradual migration from Selenium to WebDriver.
Users not wanting Selenium 2 in the classpath when using jbehave-web-selenium
can simply exclude the dependency
{code:xml}
dependency
groupIdorg.seleniumhq.selenium/groupId
artifactIdselenium/artifactId
/dependency
{code:xml}
and replace with the Selenium 1 dependency.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-343) trader-runner-stories does not include css/js/images in jbehave-reports/view
[ http://jira.codehaus.org/browse/JBEHAVE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-343: - Fix Version/s: 3.0.1 Issue Type: Task (was: Bug) Summary: trader-runner-stories does not include css/js/images in jbehave-reports/view (was: trader-runner-stories does not include css/js/images in rendered (view) reports.) trader-runner-stories does not include css/js/images in jbehave-reports/view Key: JBEHAVE-343 URL: http://jira.codehaus.org/browse/JBEHAVE-343 Project: JBehave Issue Type: Task Components: Web Runner Affects Versions: web-3.0 Reporter: Paul Hammant Priority: Minor Fix For: web-3.0.1 As an example to copy, trader-runner-stories is incomplete as the HTML reports are not styled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-343) trader-runner-stories does not include css/js/images in jbehave-reports/view
[ http://jira.codehaus.org/browse/JBEHAVE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-343: - Fix Version/s: (was: 3.0.1) web-3.0.1 Assignee: Mauro Talevi trader-runner-stories does not include css/js/images in jbehave-reports/view Key: JBEHAVE-343 URL: http://jira.codehaus.org/browse/JBEHAVE-343 Project: JBehave Issue Type: Task Components: Web Runner Affects Versions: web-3.0 Reporter: Paul Hammant Assignee: Mauro Talevi Priority: Minor Fix For: web-3.0.1 As an example to copy, trader-runner-stories is incomplete as the HTML reports are not styled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-344) @BeforeScenario failures prevent the story reporting to complete
@BeforeScenario failures prevent the story reporting to complete Key: JBEHAVE-344 URL: http://jira.codehaus.org/browse/JBEHAVE-344 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.0 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.0.1 Failures in @BeforeScenario methods should be treated as normal step failures and allow the scenario to run (while not performing the steps) and to complete the story reporting. This also allows the stats to be collected and reported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-344) @BeforeScenario failures prevent the story reporting to complete
[ http://jira.codehaus.org/browse/JBEHAVE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-344. -- Resolution: Fixed @BeforeScenario failures prevent the story reporting to complete Key: JBEHAVE-344 URL: http://jira.codehaus.org/browse/JBEHAVE-344 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.0 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.0.1 Failures in @BeforeScenario methods should be treated as normal step failures and allow the scenario to run (while not performing the steps) and to complete the story reporting. This also allows the stats to be collected and reported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-346) Add getter/setter for FilePathResolver in SpringStoryReporterBuilder
Add getter/setter for FilePathResolver in SpringStoryReporterBuilder Key: JBEHAVE-346 URL: http://jira.codehaus.org/browse/JBEHAVE-346 Project: JBehave Issue Type: Improvement Affects Versions: 3.0 Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.0.1 As noted by Pete Suggitt, the getter/setter for FilePathResolver is missing from SpringStoryReporterBuilder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-347) Method useViewGenerator in Configuration does not honour the builder pattern
Method useViewGenerator in Configuration does not honour the builder pattern Key: JBEHAVE-347 URL: http://jira.codehaus.org/browse/JBEHAVE-347 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.0 Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.0.1 Need to make the method return Configuration -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-347) Method useViewGenerator in Configuration does not honour the builder pattern
[ http://jira.codehaus.org/browse/JBEHAVE-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-347. -- Resolution: Fixed Method useViewGenerator in Configuration does not honour the builder pattern Key: JBEHAVE-347 URL: http://jira.codehaus.org/browse/JBEHAVE-347 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.0 Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.0.1 Need to make the method return Configuration -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-339) HTML report numbers could be more tabular
[ http://jira.codehaus.org/browse/JBEHAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-339: - Fix Version/s: (was: 3.1) 3.0.1 Assignee: Mauro Talevi HTML report numbers could be more tabular -- Key: JBEHAVE-339 URL: http://jira.codehaus.org/browse/JBEHAVE-339 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.0 Reporter: Paul Hammant Assignee: Mauro Talevi Fix For: 3.0.1 guice.stories.simple_guice_exampleScenarios: 1 (Failed: 0) Steps: 3 (Successful: 3; Pending: 0; Not Performed: 0; Failed: 0; Ignorable: 0) i18n.stories.fr_trader_is_alerted_of_status Scenarios: 1 (Failed: 0) Steps: 13 (Successful: 0; Pending: 4; Not Performed: 9; Failed: 0; Ignorable: 0) i18n.stories.it_trader_is_alerted_of_status Scenarios: 2 (Failed: 0) Steps: 15 (Successful: 7; Pending: 8; Not Performed: 0; Failed: 0; Ignorable: 0) The output formats as a string. There are some numbers is parens. These should really be tdnumbers/td There should also be totals at the bottom of the set, and column headings at the top :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-348) SpringStepsFactory should not try to instantiate abstract beans
[ http://jira.codehaus.org/browse/JBEHAVE-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-348. -- Resolution: Fixed SpringStepsFactory should not try to instantiate abstract beans Key: JBEHAVE-348 URL: http://jira.codehaus.org/browse/JBEHAVE-348 Project: JBehave Issue Type: Improvement Components: Spring Support Affects Versions: 3.0 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.0.1 Spring allows the declaration of abstract beans. These should be identified via their bean type and not instantiated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-339) HTML report numbers could be more tabular
[ http://jira.codehaus.org/browse/JBEHAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-339: - Fix Version/s: (was: 3.0.1) 3.0.2 HTML report numbers could be more tabular -- Key: JBEHAVE-339 URL: http://jira.codehaus.org/browse/JBEHAVE-339 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.0 Reporter: Paul Hammant Assignee: Mauro Talevi Fix For: 3.0.2 guice.stories.simple_guice_exampleScenarios: 1 (Failed: 0) Steps: 3 (Successful: 3; Pending: 0; Not Performed: 0; Failed: 0; Ignorable: 0) i18n.stories.fr_trader_is_alerted_of_status Scenarios: 1 (Failed: 0) Steps: 13 (Successful: 0; Pending: 4; Not Performed: 9; Failed: 0; Ignorable: 0) i18n.stories.it_trader_is_alerted_of_status Scenarios: 2 (Failed: 0) Steps: 15 (Successful: 7; Pending: 8; Not Performed: 0; Failed: 0; Ignorable: 0) The output formats as a string. There are some numbers is parens. These should really be tdnumbers/td There should also be totals at the bottom of the set, and column headings at the top :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-139) Convert ant build to use ivy for dependencies
[ http://jira.codehaus.org/browse/JBEHAVE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-139. -- Resolution: Won't Fix Convert ant build to use ivy for dependencies - Key: JBEHAVE-139 URL: http://jira.codehaus.org/browse/JBEHAVE-139 Project: JBehave Issue Type: Improvement Components: Build Affects Versions: 2.0 Environment: Any Reporter: Dan North Assignee: Dan North We currently have a lib directory with various subdirectories containing a number of dependent jars. As we add more adapters (spring, pico, test-ng) this is going to get more complex. Ivy (http://ant.apache.org/ivy) has a similar dependency resolution model to maven. By migrating to ivy we can simplify the build and remove the dependent third-party jars from the repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-115) Undoable steps
[ http://jira.codehaus.org/browse/JBEHAVE-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-115. -- Resolution: Duplicate Resolving as duplicate of JBEHAVE-129, until someone comes up with a more elaborate use case. Undoable steps -- Key: JBEHAVE-115 URL: http://jira.codehaus.org/browse/JBEHAVE-115 Project: JBehave Issue Type: New Feature Reporter: Elizabeth Keogh Sometimes when we set up a context or cause an event to happen, it's nice to clean up any changes so that we don't affect other tests running. No idea how to make the undoable work, but doesn't stop me wanting it! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Commented: (JBEHAVE-146) PendingErrorStrategy choices needs one more.
[
http://jira.codehaus.org/browse/JBEHAVE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=236361#action_236361
]
Mauro Talevi commented on JBEHAVE-146:
--
Paul, do you feel you still need more choices?
PendingErrorStrategy choices needs one more.
Key: JBEHAVE-146
URL: http://jira.codehaus.org/browse/JBEHAVE-146
Project: JBehave
Issue Type: Wish
Affects Versions: 2.1
Reporter: Paul Hammant
PASSING and SILENT are identical method bodies
The same is true of FAILING and RETHROW
[ moving past that issue ]
Could y'all make one more strategy ?
{noformat}
/**
* This will continue the scenario as PASSING would, but at the end,
remember that there was an issue during the run, and throw it again then.
*/
PendingErrorStrategy FAIL_LATER = new PendingErrorStrategy() {
public void handleError(Throwable throwable) {
// ??
}
};
{noformat}
Note, I've even given you some /** Javadoc */ for this, as
http://jbehave.org/javadoc/latest/core/org/jbehave/scenario/errors/PendingErrorStrategy.html
is a little sparse on information ;-)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Commented: (JBEHAVE-146) PendingErrorStrategy choices needs one more.
[
http://jira.codehaus.org/browse/JBEHAVE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=236362#action_236362
]
Mauro Talevi commented on JBEHAVE-146:
--
Paul, do you feel you still need more choices?
PendingErrorStrategy choices needs one more.
Key: JBEHAVE-146
URL: http://jira.codehaus.org/browse/JBEHAVE-146
Project: JBehave
Issue Type: Wish
Affects Versions: 2.1
Reporter: Paul Hammant
PASSING and SILENT are identical method bodies
The same is true of FAILING and RETHROW
[ moving past that issue ]
Could y'all make one more strategy ?
{noformat}
/**
* This will continue the scenario as PASSING would, but at the end,
remember that there was an issue during the run, and throw it again then.
*/
PendingErrorStrategy FAIL_LATER = new PendingErrorStrategy() {
public void handleError(Throwable throwable) {
// ??
}
};
{noformat}
Note, I've even given you some /** Javadoc */ for this, as
http://jbehave.org/javadoc/latest/core/org/jbehave/scenario/errors/PendingErrorStrategy.html
is a little sparse on information ;-)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-260) Improve SpringStepsFactory to allow delegating the CandidateStep creation to other factories
[
http://jira.codehaus.org/browse/JBEHAVE-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-260.
--
Resolution: Fixed
Fix Version/s: 3.0.2
SpringStepsFactory provides protected method:
{code}
protected ListObject stepsInstances();
{code}
Improve SpringStepsFactory to allow delegating the CandidateStep creation to
other factories
Key: JBEHAVE-260
URL: http://jira.codehaus.org/browse/JBEHAVE-260
Project: JBehave
Issue Type: Improvement
Components: Core
Affects Versions: 2.5.1
Reporter: Bruno Bieth
Fix For: 3.0.2
Change the SpringStepsFactory so it doesn't create CandidateSteps but rather
return bean instances. That way I can have a different way of instanciating
CandidateSteps.
{code}
addSteps(new ParameterConverterStepsFactory().createCandidateSteps( new
SpringStepsFactory(context).createStepsInstances() ));
{code}
And the simplified SpringStepsFactory :
{code}
public class SpringStepsFactory {
private final ListableBeanFactory parent;
public SpringStepsFactory(ListableBeanFactory parent) {
this.parent = parent;
}
public Object[] createStepsInstances() {
ListObject steps = new ArrayListObject();
for (String name : parent.getBeanDefinitionNames()) {
Object bean = parent.getBean(name);
if (containsScenarioAnnotations(bean.getClass())) {
steps.add(bean);
}
}
return steps.toArray(new Object[steps.size()]);
}
private boolean containsScenarioAnnotations(Class? componentClass) {
for (Method method : componentClass.getMethods()) {
for (Annotation annotation : method.getAnnotations()) {
if
(annotation.annotationType().getName().startsWith(org.jbehave.scenario.annotations))
{
return true;
}
}
}
return false;
}
}
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-349) SpringStepsFactory should ignore beans with undefined type and that fail instantiation
[ http://jira.codehaus.org/browse/JBEHAVE-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-349: - Summary: SpringStepsFactory should ignore beans with undefined type and that fail instantiation (was: JBehave Spring doesn't work with abstract beans) SpringStepsFactory should ignore beans with undefined type and that fail instantiation -- Key: JBEHAVE-349 URL: http://jira.codehaus.org/browse/JBEHAVE-349 Project: JBehave Issue Type: Bug Components: Spring Support Affects Versions: 3.0.1 Reporter: Tom Marsh Assignee: Mauro Talevi Priority: Critical Fix For: 3.0.2 Attachments: [tmarsh]_Fixing_abstract_bean_error.patch If you use abstract beans the annotation processor blows up. I've included a patch. Its basically a try catch around the getBean step. Test data enhanced to recreate problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Work started: (JBEHAVE-339) HTML report numbers could be more tabular
[ http://jira.codehaus.org/browse/JBEHAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-339 started by Mauro Talevi. HTML report numbers could be more tabular -- Key: JBEHAVE-339 URL: http://jira.codehaus.org/browse/JBEHAVE-339 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.0 Reporter: Paul Hammant Assignee: Mauro Talevi Fix For: 3.0.2 guice.stories.simple_guice_exampleScenarios: 1 (Failed: 0) Steps: 3 (Successful: 3; Pending: 0; Not Performed: 0; Failed: 0; Ignorable: 0) i18n.stories.fr_trader_is_alerted_of_status Scenarios: 1 (Failed: 0) Steps: 13 (Successful: 0; Pending: 4; Not Performed: 9; Failed: 0; Ignorable: 0) i18n.stories.it_trader_is_alerted_of_status Scenarios: 2 (Failed: 0) Steps: 15 (Successful: 7; Pending: 8; Not Performed: 0; Failed: 0; Ignorable: 0) The output formats as a string. There are some numbers is parens. These should really be tdnumbers/td There should also be totals at the bottom of the set, and column headings at the top :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Commented: (JBEHAVE-339) HTML report numbers could be more tabular
[ http://jira.codehaus.org/browse/JBEHAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=236451#action_236451 ] Mauro Talevi commented on JBEHAVE-339: -- Added view template ftl/jbehave-reports-index-with-totals.ftl which supports a more tabular layout and has totals by column. Made new view the default, but the previous view ftl/jbehave-reports-index.ftl is still available and can be configured (see trader-i18n example). HTML report numbers could be more tabular -- Key: JBEHAVE-339 URL: http://jira.codehaus.org/browse/JBEHAVE-339 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.0 Reporter: Paul Hammant Assignee: Mauro Talevi Fix For: 3.0.2 guice.stories.simple_guice_exampleScenarios: 1 (Failed: 0) Steps: 3 (Successful: 3; Pending: 0; Not Performed: 0; Failed: 0; Ignorable: 0) i18n.stories.fr_trader_is_alerted_of_status Scenarios: 1 (Failed: 0) Steps: 13 (Successful: 0; Pending: 4; Not Performed: 9; Failed: 0; Ignorable: 0) i18n.stories.it_trader_is_alerted_of_status Scenarios: 2 (Failed: 0) Steps: 15 (Successful: 7; Pending: 8; Not Performed: 0; Failed: 0; Ignorable: 0) The output formats as a string. There are some numbers is parens. These should really be tdnumbers/td There should also be totals at the bottom of the set, and column headings at the top :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-350) Collect successful scenarios stat and render in story reports
Collect successful scenarios stat and render in story reports - Key: JBEHAVE-350 URL: http://jira.codehaus.org/browse/JBEHAVE-350 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.0.1, 3.0 Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.0.2 Currently, only the number of run scenarios and failed scenarios are collected. Collecting also the number of successful makes it easier to highlight in green just the number of successful ones. Now we are highlighting the total number of scenarios in green when there are failures, and this is confusing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-339) HTML report numbers could be more tabular
[ http://jira.codehaus.org/browse/JBEHAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-339. -- Resolution: Fixed HTML report numbers could be more tabular -- Key: JBEHAVE-339 URL: http://jira.codehaus.org/browse/JBEHAVE-339 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.0 Reporter: Paul Hammant Assignee: Mauro Talevi Fix For: 3.0.2 guice.stories.simple_guice_exampleScenarios: 1 (Failed: 0) Steps: 3 (Successful: 3; Pending: 0; Not Performed: 0; Failed: 0; Ignorable: 0) i18n.stories.fr_trader_is_alerted_of_status Scenarios: 1 (Failed: 0) Steps: 13 (Successful: 0; Pending: 4; Not Performed: 9; Failed: 0; Ignorable: 0) i18n.stories.it_trader_is_alerted_of_status Scenarios: 2 (Failed: 0) Steps: 15 (Successful: 7; Pending: 8; Not Performed: 0; Failed: 0; Ignorable: 0) The output formats as a string. There are some numbers is parens. These should really be tdnumbers/td There should also be totals at the bottom of the set, and column headings at the top :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-343) Trader runner stories examples do not include css/js/images in jbehave-reports/view
[ http://jira.codehaus.org/browse/JBEHAVE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-343: - Component/s: (was: Web Runner) Description: As an example to copy, trader runner stories are incomplete as the HTML reports are not styled. (was: As an example to copy, trader-runner-stories is incomplete as the HTML reports are not styled.) Fix Version/s: (was: web-3.0.1) web-3.1 Summary: Trader runner stories examples do not include css/js/images in jbehave-reports/view (was: trader-runner-stories does not include css/js/images in jbehave-reports/view) Trader runner stories examples do not include css/js/images in jbehave-reports/view --- Key: JBEHAVE-343 URL: http://jira.codehaus.org/browse/JBEHAVE-343 Project: JBehave Issue Type: Task Affects Versions: web-3.0 Reporter: Paul Hammant Assignee: Mauro Talevi Priority: Minor Fix For: web-3.1 As an example to copy, trader runner stories are incomplete as the HTML reports are not styled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-343) Trader runner stories examples do not include css/js/images in jbehave-reports/view
[ http://jira.codehaus.org/browse/JBEHAVE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-343. -- Resolution: Fixed Trader runner stories examples do not include css/js/images in jbehave-reports/view --- Key: JBEHAVE-343 URL: http://jira.codehaus.org/browse/JBEHAVE-343 Project: JBehave Issue Type: Task Affects Versions: web-3.0 Reporter: Paul Hammant Assignee: Mauro Talevi Priority: Minor Fix For: web-3.1 As an example to copy, trader runner stories are incomplete as the HTML reports are not styled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Assigned: (JBEHAVE-345) Add WebDriver support
[ http://jira.codehaus.org/browse/JBEHAVE-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-345: Assignee: Paul Hammant Add WebDriver support - Key: JBEHAVE-345 URL: http://jira.codehaus.org/browse/JBEHAVE-345 Project: JBehave Issue Type: New Feature Components: Web Selenium Reporter: Mauro Talevi Assignee: Paul Hammant Fix For: web-3.1 Added support for WebDriver, similarly to support for Selenium. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Assigned: (JBEHAVE-345) Add WebDriver support
[ http://jira.codehaus.org/browse/JBEHAVE-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-345: Assignee: Mauro Talevi (was: Paul Hammant) Add WebDriver support - Key: JBEHAVE-345 URL: http://jira.codehaus.org/browse/JBEHAVE-345 Project: JBehave Issue Type: New Feature Components: Web Selenium Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.1 Added support for WebDriver, similarly to support for Selenium. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Work started: (JBEHAVE-345) Add WebDriver support
[ http://jira.codehaus.org/browse/JBEHAVE-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-345 started by Mauro Talevi. Add WebDriver support - Key: JBEHAVE-345 URL: http://jira.codehaus.org/browse/JBEHAVE-345 Project: JBehave Issue Type: New Feature Components: Web Selenium Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.1 Added support for WebDriver, similarly to support for Selenium. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Assigned: (JBEHAVE-351) ContextView for communicating the current context
[ http://jira.codehaus.org/browse/JBEHAVE-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-351: Assignee: Mauro Talevi ContextView for communicating the current context - Key: JBEHAVE-351 URL: http://jira.codehaus.org/browse/JBEHAVE-351 Project: JBehave Issue Type: New Feature Components: Web Selenium Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.1 Selenium API has a nice feature Selenium#setContext(String) which shows up in the Selenium server window. This feature is not available to WebDriver (no separate server window running anymore). By having a ContextView abstraction we can then provide alternative impls, such as a Swing-based panel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-351) ContextView for communicating the current context
ContextView for communicating the current context - Key: JBEHAVE-351 URL: http://jira.codehaus.org/browse/JBEHAVE-351 Project: JBehave Issue Type: New Feature Components: Web Selenium Reporter: Mauro Talevi Fix For: web-3.1 Selenium API has a nice feature Selenium#setContext(String) which shows up in the Selenium server window. This feature is not available to WebDriver (no separate server window running anymore). By having a ContextView abstraction we can then provide alternative impls, such as a Swing-based panel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-352) Allow comments in tables
[ http://jira.codehaus.org/browse/JBEHAVE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-352: - Component/s: Core Fix Version/s: 3.0.3 Issue Type: Improvement (was: Bug) Summary: Allow comments in tables (was: Table parsing stops when a comment is found) Allow comments in tables Key: JBEHAVE-352 URL: http://jira.codehaus.org/browse/JBEHAVE-352 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 2.5.8, 2.5.9, 3.0 Reporter: Andy Peel Priority: Minor Fix For: 3.0.3 We'd like to be able to include comments in tables to make scenarios clearer, but JBehave refuses to read in the lines after the comment in this example, leading to zero rows being created in the resulting ExamplesTable. Given the documents: |a|b|c| !-- I'd like to have a comment here |1|2|3| |4|5|6| |1|2|3| I've tried a small test with 2.5.9 and 3.0 of JBehave but they don't fix the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-354) @Given, @When and @Then could make the string optional ....
[
http://jira.codehaus.org/browse/JBEHAVE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-354:
-
Description:
... in that case the Java method that it pertains to could provide the matching
expression:
{code}
@Given
public void aUserWithALargeBankBalance { .. }
{code}
would be equiv to
{code}
@Given(a user with a large bank balance)
public void aUserWithALargeBankBalance { .. }
{code}
or maybe we could endorse Ruby naming conventions for extra capitalization
clarity:
| @Given
| public void a_user_with_a_large_bank_balance { .. }
Obviously this is no good for cases where there are parameters. Though that
could be solved too later, with yet more work.
Guilherme Silveira's idea :)
was:
... in that case the Java method that it pertains to could provide the matching
expression:
| @Given
| public void aUserWithALargeBankBalance { .. }
would be equiv to
| @Given(a user with a large bank balance)
| public void aUserWithALargeBankBalance { .. }
or maybe we could endorse Ruby naming conventions for extra capitalization
clarity:
| @Given
| public void a_user_with_a_large_bank_balance { .. }
Obviously this is no good for cases where there are parameters. Though that
could be solved too later, with yet more work.
Guilherme Silveira's idea :)
Fix Version/s: 3.1
@Given, @When and @Then could make the string optional
---
Key: JBEHAVE-354
URL: http://jira.codehaus.org/browse/JBEHAVE-354
Project: JBehave
Issue Type: Improvement
Components: Core
Reporter: Paul Hammant
Fix For: 3.1
... in that case the Java method that it pertains to could provide the
matching expression:
{code}
@Given
public void aUserWithALargeBankBalance { .. }
{code}
would be equiv to
{code}
@Given(a user with a large bank balance)
public void aUserWithALargeBankBalance { .. }
{code}
or maybe we could endorse Ruby naming conventions for extra capitalization
clarity:
| @Given
| public void a_user_with_a_large_bank_balance { .. }
Obviously this is no good for cases where there are parameters. Though that
could be solved too later, with yet more work.
Guilherme Silveira's idea :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-354) @Given, @When and @Then could make the pattern optional
[
http://jira.codehaus.org/browse/JBEHAVE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-354:
-
Summary: @Given, @When and @Then could make the pattern optional (was:
@Given, @When and @Then could make the string optional )
@Given, @When and @Then could make the pattern optional
---
Key: JBEHAVE-354
URL: http://jira.codehaus.org/browse/JBEHAVE-354
Project: JBehave
Issue Type: Improvement
Components: Core
Reporter: Paul Hammant
Fix For: 3.1
... in that case the Java method that it pertains to could provide the
matching expression:
{code}
@Given
public void aUserWithALargeBankBalance { .. }
{code}
would be equiv to
{code}
@Given(a user with a large bank balance)
public void aUserWithALargeBankBalance { .. }
{code}
or maybe we could endorse Ruby naming conventions for extra capitalization
clarity:
| @Given
| public void a_user_with_a_large_bank_balance { .. }
Obviously this is no good for cases where there are parameters. Though that
could be solved too later, with yet more work.
Guilherme Silveira's idea :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-354) @Given, @When and @Then could make the pattern optional
[
http://jira.codehaus.org/browse/JBEHAVE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-354:
-
Description:
... in that case the Java method that it pertains to could provide the matching
expression:
{code}
@Given
public void aUserWithALargeBankBalance { .. }
{code}
would be equiv to
{code}
@Given(a user with a large bank balance)
public void aUserWithALargeBankBalance { .. }
{code}
or maybe we could endorse Ruby naming conventions for extra capitalization
clarity:
{code}
@Given
public void a_user_with_a_large_bank_balance { .. }
{code}
Obviously this is no good for cases where there are parameters. Though that
could be solved too later, with yet more work.
Guilherme Silveira's idea :)
was:
... in that case the Java method that it pertains to could provide the matching
expression:
{code}
@Given
public void aUserWithALargeBankBalance { .. }
{code}
would be equiv to
{code}
@Given(a user with a large bank balance)
public void aUserWithALargeBankBalance { .. }
{code}
or maybe we could endorse Ruby naming conventions for extra capitalization
clarity:
| @Given
| public void a_user_with_a_large_bank_balance { .. }
Obviously this is no good for cases where there are parameters. Though that
could be solved too later, with yet more work.
Guilherme Silveira's idea :)
Just noted the comment on the fact that one could also consider the case of
parameters. Don't see how, unless one goes into all sort of strange
conventions. I think that would complicate a model which is at present quite
simple and allow a nice separation between the pattern and the method name.
@Given, @When and @Then could make the pattern optional
---
Key: JBEHAVE-354
URL: http://jira.codehaus.org/browse/JBEHAVE-354
Project: JBehave
Issue Type: Improvement
Components: Core
Reporter: Paul Hammant
Fix For: 3.1
... in that case the Java method that it pertains to could provide the
matching expression:
{code}
@Given
public void aUserWithALargeBankBalance { .. }
{code}
would be equiv to
{code}
@Given(a user with a large bank balance)
public void aUserWithALargeBankBalance { .. }
{code}
or maybe we could endorse Ruby naming conventions for extra capitalization
clarity:
{code}
@Given
public void a_user_with_a_large_bank_balance { .. }
{code}
Obviously this is no good for cases where there are parameters. Though that
could be solved too later, with yet more work.
Guilherme Silveira's idea :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-353) Empty example table row values cause exception
[ http://jira.codehaus.org/browse/JBEHAVE-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-353. -- Resolution: Fixed Empty table row values are now allowed. Empty example table row values cause exception -- Key: JBEHAVE-353 URL: http://jira.codehaus.org/browse/JBEHAVE-353 Project: JBehave Issue Type: Bug Components: Core Environment: JBehave core 3.0.2 Reporter: Frank Grimm Assignee: Mauro Talevi Priority: Minor Fix For: 3.0.3 Given the following example table: |C1|C2|C3| JBehave fails to parse the table. It reports the following error: |C1|C2|C3| (FAILED) (java.lang.IndexOutOfBoundsException: Index: 0, Size: 0) The stack trace reads: Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.remove(ArrayList.java:387) at org.jbehave.core.model.ExamplesTable.columnsFor(ExamplesTable.java:76) at org.jbehave.core.model.ExamplesTable.parse(ExamplesTable.java:60) at org.jbehave.core.model.ExamplesTable.init(ExamplesTable.java:48) at org.jbehave.core.steps.ParameterConverters$ExamplesTableConverter.convertValue(ParameterConverters.java:328) at org.jbehave.core.steps.ParameterConverters.convert(ParameterConverters.java:68) at org.jbehave.core.steps.StepCreator.convertParameters(StepCreator.java:253) at org.jbehave.core.steps.StepCreator.access$1100(StepCreator.java:25) at org.jbehave.core.steps.StepCreator$5.parametriseStep(StepCreator.java:161) at org.jbehave.core.steps.StepCreator$5.perform(StepCreator.java:129) at org.jbehave.core.embedder.StoryRunner$FineSoFar.run(StoryRunner.java:189) at org.jbehave.core.embedder.StoryRunner.runSteps(StoryRunner.java:174) at org.jbehave.core.embedder.StoryRunner.runScenarioSteps(StoryRunner.java:162) at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:84) at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:62) at org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:160) ... 43 more Parsing the table works fine if the last row contains at least one space in one of the cells. So |C1|C2|C3| ||| | and |C1|C2|C3| || || works fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Assigned: (JBEHAVE-353) Empty example table row values cause exception
[ http://jira.codehaus.org/browse/JBEHAVE-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-353: Assignee: Mauro Talevi Empty example table row values cause exception -- Key: JBEHAVE-353 URL: http://jira.codehaus.org/browse/JBEHAVE-353 Project: JBehave Issue Type: Bug Components: Core Environment: JBehave core 3.0.2 Reporter: Frank Grimm Assignee: Mauro Talevi Priority: Minor Fix For: 3.0.3 Given the following example table: |C1|C2|C3| JBehave fails to parse the table. It reports the following error: |C1|C2|C3| (FAILED) (java.lang.IndexOutOfBoundsException: Index: 0, Size: 0) The stack trace reads: Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.remove(ArrayList.java:387) at org.jbehave.core.model.ExamplesTable.columnsFor(ExamplesTable.java:76) at org.jbehave.core.model.ExamplesTable.parse(ExamplesTable.java:60) at org.jbehave.core.model.ExamplesTable.init(ExamplesTable.java:48) at org.jbehave.core.steps.ParameterConverters$ExamplesTableConverter.convertValue(ParameterConverters.java:328) at org.jbehave.core.steps.ParameterConverters.convert(ParameterConverters.java:68) at org.jbehave.core.steps.StepCreator.convertParameters(StepCreator.java:253) at org.jbehave.core.steps.StepCreator.access$1100(StepCreator.java:25) at org.jbehave.core.steps.StepCreator$5.parametriseStep(StepCreator.java:161) at org.jbehave.core.steps.StepCreator$5.perform(StepCreator.java:129) at org.jbehave.core.embedder.StoryRunner$FineSoFar.run(StoryRunner.java:189) at org.jbehave.core.embedder.StoryRunner.runSteps(StoryRunner.java:174) at org.jbehave.core.embedder.StoryRunner.runScenarioSteps(StoryRunner.java:162) at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:84) at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:62) at org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:160) ... 43 more Parsing the table works fine if the last row contains at least one space in one of the cells. So |C1|C2|C3| ||| | and |C1|C2|C3| || || works fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-356) Update ParameterConvertersBehaviour to support non-English default locales
[ http://jira.codehaus.org/browse/JBEHAVE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-356. -- Resolution: Fixed Update ParameterConvertersBehaviour to support non-English default locales -- Key: JBEHAVE-356 URL: http://jira.codehaus.org/browse/JBEHAVE-356 Project: JBehave Issue Type: Task Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.0.3 Contributed via Github by Gilles Scokart (http://github.com/gscokart) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-356) Update ParameterConvertersBehaviour to support non-English default locales
Update ParameterConvertersBehaviour to support non-English default locales -- Key: JBEHAVE-356 URL: http://jira.codehaus.org/browse/JBEHAVE-356 Project: JBehave Issue Type: Task Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.0.3 Contributed via Github by Gilles Scokart (http://github.com/gscokart) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-357) Add pom.xml to binary distribution
Add pom.xml to binary distribution -- Key: JBEHAVE-357 URL: http://jira.codehaus.org/browse/JBEHAVE-357 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi Priority: Minor Fix For: 3.1 As suggested by Mike DuVall on list, adding the pom.xml to binary distro is helpful. Update DEPENDENCIES.txt accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-358) Add Story Map/Theme views
Add Story Map/Theme views - Key: JBEHAVE-358 URL: http://jira.codehaus.org/browse/JBEHAVE-358 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Fix For: 3.1 In order to get visibility of themes/epics As a release planner I want to be able to view stories by theme/epic. Using story maps allows us to group stories of cross-cutting concerns. Themes/epics can be specified directly at story level using Meta info (JBEHAVE-220) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Work started: (JBEHAVE-220) Allow per-story and per-scenario meta-information
[ http://jira.codehaus.org/browse/JBEHAVE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-220 started by Mauro Talevi. Allow per-story and per-scenario meta-information - Key: JBEHAVE-220 URL: http://jira.codehaus.org/browse/JBEHAVE-220 Project: JBehave Issue Type: New Feature Components: Core Reporter: Chris Jensen Assignee: Mauro Talevi Fix For: 3.1 From a development management perspective, BDD could be extremely useful in helping to track and understand who is creating specifications and when they are being injected. Since requirements like this will vary between users, it would be a good idea to implement as generically as possible and then provide an example or reference. My thoughts on what would be useful in my own situation: - A way to indicate the Author(s) of a scenario - A way to indicate the Owner of a story - A way to indicate the Creation Date of a scenario - A way to indicate the Last Update Date of a scenario - The injection phase of the scenario (eg. grooming, planning, development...) I don't think these should be included in the grammar as individual, specific elements, but perhaps the grammar could have a syntax for optional meta-information. The grammar would allow a word (eg. Meta:) followed by a category, perhaps emphasized with a symbol (eg. @Author) and then followed by any arbitrary text. This would allow interesting things... Meta: @Author John Meta: @Role Product Owner Meta: @Created 2009-11-08 Meta: @Injection Backlog Grooming -OR- Meta: @Author Fred Meta: @Role Quality Engineer Meta: @Created 2009-12-02 Meta: @Injection Sprint Planning -OR- Meta: @Author Colin Meta: @Role Developer Meta: @Created 2009-12-10 Meta: @Injection Development Being able to say that, for instance, only 20% of scenarios are created in backlog grooming, while another 20% are created in sprint planning and 60% are created during development would be very useful in identifying and resolving process impediments and training product owners and teams to define requirements earlier so they don't run into velocity impacts when they are discovered late in a sprint. Allowing meta-data would enable scenario management tool development. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Assigned: (JBEHAVE-357) Add pom.xml to binary distribution
[ http://jira.codehaus.org/browse/JBEHAVE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-357: Assignee: Mauro Talevi Add pom.xml to binary distribution -- Key: JBEHAVE-357 URL: http://jira.codehaus.org/browse/JBEHAVE-357 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1 As suggested by Mike DuVall on list, adding the pom.xml to binary distro is helpful. Update DEPENDENCIES.txt accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-357) Add pom.xml to binary distribution
[ http://jira.codehaus.org/browse/JBEHAVE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-357. -- Resolution: Fixed Add pom.xml to binary distribution -- Key: JBEHAVE-357 URL: http://jira.codehaus.org/browse/JBEHAVE-357 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1 As suggested by Mike DuVall on list, adding the pom.xml to binary distro is helpful. Update DEPENDENCIES.txt accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-220) Allow per-story and per-scenario meta-information
[ http://jira.codehaus.org/browse/JBEHAVE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-220. -- Resolution: Fixed Allow per-story and per-scenario meta-information - Key: JBEHAVE-220 URL: http://jira.codehaus.org/browse/JBEHAVE-220 Project: JBehave Issue Type: New Feature Components: Core Reporter: Chris Jensen Assignee: Mauro Talevi Fix For: 3.1 From a development management perspective, BDD could be extremely useful in helping to track and understand who is creating specifications and when they are being injected. Since requirements like this will vary between users, it would be a good idea to implement as generically as possible and then provide an example or reference. My thoughts on what would be useful in my own situation: - A way to indicate the Author(s) of a scenario - A way to indicate the Owner of a story - A way to indicate the Creation Date of a scenario - A way to indicate the Last Update Date of a scenario - The injection phase of the scenario (eg. grooming, planning, development...) I don't think these should be included in the grammar as individual, specific elements, but perhaps the grammar could have a syntax for optional meta-information. The grammar would allow a word (eg. Meta:) followed by a category, perhaps emphasized with a symbol (eg. @Author) and then followed by any arbitrary text. This would allow interesting things... Meta: @Author John @Role Product Owner @Created 2009-11-08 @Injection Backlog Grooming -OR- Meta: @Author Fred @Role Quality Engineer @Created 2009-12-02 @Injection Sprint Planning -OR- Meta: @Author Colin @Role Developer @Created 2009-12-10 @Injection Development Being able to say that, for instance, only 20% of scenarios are created in backlog grooming, while another 20% are created in sprint planning and 60% are created during development would be very useful in identifying and resolving process impediments and training product owners and teams to define requirements earlier so they don't run into velocity impacts when they are discovered late in a sprint. Allowing meta-data would enable scenario management tool development. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-316) Define commom JAXB interfaces for systems to provide Features and its Stories and Scenarios to a JBehave runner.
[ http://jira.codehaus.org/browse/JBEHAVE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-316: - Fix Version/s: (was: 3.1) 3.2 Define commom JAXB interfaces for systems to provide Features and its Stories and Scenarios to a JBehave runner. Key: JBEHAVE-316 URL: http://jira.codehaus.org/browse/JBEHAVE-316 Project: JBehave Issue Type: New Feature Components: Core Affects Versions: 3.0 Reporter: Cristiano Gavião Fix For: 3.2 There are many systems where Stories could be writed, stored and mantained. Some example are Confluence (using its excelent versioning handle), Rational RSA, SparxSystems Enterprise Architect (both as scenarios inside UseCases/Features UML elements). One way todo that integration would be Jbehave to provide commom classes annotated with _javax.xml.bind.annotation.Xml*_ where developers could create JAXB *Services* that will get data from whatevers system and serve Features, its Stories and related Scenarios objects for JBehave as XML ou JSON. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Assigned: (JBEHAVE-360) Improve tabular story report
[ http://jira.codehaus.org/browse/JBEHAVE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-360: Assignee: Mauro Talevi Improve tabular story report - Key: JBEHAVE-360 URL: http://jira.codehaus.org/browse/JBEHAVE-360 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.0.2 Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1 Feedback from colleagues' first use of tabular story report introduced in 3.0.2 (JBEHAVE-339). - The layout is too dispersive, too much white space and table runs away out of page - Unnecessary (or misleading) repetitions of column headers, such as Successful and Failed - More difficult to spot failures, only numbers are colour-coded Suggestions include: - Have a top-level multi-column row with two headers, Scenarios and Steps. - Use logos (with hovering text) for Successful, Failed, Pending etc ... - Colour-code in red the story name in case of failure -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-358) Add Story Mapping with Swimlane view
[ http://jira.codehaus.org/browse/JBEHAVE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-358: - Description: In order to get visibility of themes/epics As a release planner I want to be able to map stories by meta filters Using story maps allows us to group stories of cross-cutting concerns, using filters on meta info (JBEHAVE-220). A swimlane view (with one lane per filter) would allow a clear and concise view. was: In order to get visibility of themes/epics As a release planner I want to be able to view stories by theme/epic. Using story maps allows us to group stories of cross-cutting concerns. Themes/epics can be specified directly at story level using Meta info (JBEHAVE-220) Summary: Add Story Mapping with Swimlane view (was: Add Story Map/Theme views) Add Story Mapping with Swimlane view Key: JBEHAVE-358 URL: http://jira.codehaus.org/browse/JBEHAVE-358 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Fix For: 3.1 In order to get visibility of themes/epics As a release planner I want to be able to map stories by meta filters Using story maps allows us to group stories of cross-cutting concerns, using filters on meta info (JBEHAVE-220). A swimlane view (with one lane per filter) would allow a clear and concise view. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Assigned: (JBEHAVE-362) Convert story name in report to human readable form
[ http://jira.codehaus.org/browse/JBEHAVE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-362: Assignee: Mauro Talevi Convert story name in report to human readable form --- Key: JBEHAVE-362 URL: http://jira.codehaus.org/browse/JBEHAVE-362 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1 Another good suggestion from feedback. Convert: - trader_sells_stocks.story - Trader Sells Stocks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-359) Allow filtering of stories and scenarios based on meta-info
[ http://jira.codehaus.org/browse/JBEHAVE-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-359. -- Resolution: Fixed Allow filtering of stories and scenarios based on meta-info --- Key: JBEHAVE-359 URL: http://jira.codehaus.org/browse/JBEHAVE-359 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.1 Once we have meta-info available in our stories and scenarios (JBEHAVE-220) we can use this info to filter what is being run. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-328) Creation of a new parser to support the tracking of line numbers in error reporting.
[ http://jira.codehaus.org/browse/JBEHAVE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-328: - Fix Version/s: (was: 3.1) 3.2 Creation of a new parser to support the tracking of line numbers in error reporting. Key: JBEHAVE-328 URL: http://jira.codehaus.org/browse/JBEHAVE-328 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.1 Reporter: Mike Neeve Fix For: 3.2 Attachments: jbehave-core.patch Attached is a patch for JBehave. The main change is the addition of a new parser. Its based on Eclipse JFace, which means we can track line numbers in error reporting. It can also be re-used for syntax highlighting in an Eclipse editor. JFace requires some Eclipse libraries, so these are new dependencies which still work even though we're not running in an OSGi container. The parser is also very fast compared to the current regex-based parser - the longest running test was 25s for the previous parser, and now its just 0.5s. In ScenarioParserBehaviour we've written some tests for the default configuration of JUnitScenario. They fail with the current parser but pass with the new one which is able to throw a new ParseException for each type of problem. We've added one test to CandidateStepBehaviour.java that currently fails. Doug tried fixing it by changing the ExamplesTable to be backed by a LinkedHashMap which means that the arguments are automatically in the correct order. But this did not work for other examples and couldn't figure out how to make it work, so the test is currently broken. We'd need help to fix this. Further proposed changes would improve the detection of problems such as: - not having enough columns in the examples section to cover all the required variables - having more columns than required in the examples section - checking the order of statements e.g. ensure a When comes after a Given - allowing boolean's for parameters The first two are quite difficult as it involves a good knowledge of the CandidateStep class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Work started: (JBEHAVE-365) Add Groovy support
[ http://jira.codehaus.org/browse/JBEHAVE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-365 started by Mauro Talevi. Add Groovy support -- Key: JBEHAVE-365 URL: http://jira.codehaus.org/browse/JBEHAVE-365 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.1 Starting from Adriano Bonat's contribution via GitHub (http://github.com/tanob/jbehave-core), add a jbehave-groovy module with extensions of core for Groovy-specific support, similarly to IOC framework extensions (Guice, Pico, Spring). Initially, it will contain a GroovyStepsFactory to create steps instances from Groovy scripts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-365) Add Groovy support
[ http://jira.codehaus.org/browse/JBEHAVE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-365: - Component/s: (was: Core) Groovy Support Description: Starting from Adriano Bonat's contribution via GitHub (http://github.com/tanob/jbehave-core), add a jbehave-groovy module with extensions of core for Groovy-specific support, similarly to IOC framework extensions (Guice, Pico, Spring). Initially, it will contain a GroovyStepsFactory to create steps instances from Groovy scripts. It should also provide support for @UsingGroovy annotation, to specify the GroovyClassLoader and the GroovyResourceFinder. was: Starting from Adriano Bonat's contribution via GitHub (http://github.com/tanob/jbehave-core), add a jbehave-groovy module with extensions of core for Groovy-specific support, similarly to IOC framework extensions (Guice, Pico, Spring). Initially, it will contain a GroovyStepsFactory to create steps instances from Groovy scripts. Add Groovy support -- Key: JBEHAVE-365 URL: http://jira.codehaus.org/browse/JBEHAVE-365 Project: JBehave Issue Type: New Feature Components: Groovy Support Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.1 Starting from Adriano Bonat's contribution via GitHub (http://github.com/tanob/jbehave-core), add a jbehave-groovy module with extensions of core for Groovy-specific support, similarly to IOC framework extensions (Guice, Pico, Spring). Initially, it will contain a GroovyStepsFactory to create steps instances from Groovy scripts. It should also provide support for @UsingGroovy annotation, to specify the GroovyClassLoader and the GroovyResourceFinder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-366) Upgrade to use SyntaxHighlighter 3 for reports
Upgrade to use SyntaxHighlighter 3 for reports -- Key: JBEHAVE-366 URL: http://jira.codehaus.org/browse/JBEHAVE-366 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1 Amongst other things it does not use Flash and IE would stop winging. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-367) Add StoryFinder.findPaths(URL,String,String)
Add StoryFinder.findPaths(URL,String,String) Key: JBEHAVE-367 URL: http://jira.codehaus.org/browse/JBEHAVE-367 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.1 A very common use case is to look up paths using a URL code location. Moreover the single include/exclude pattern is also by far the most used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-367) Add to StoryFinder method to find paths by URL code location and single include/exclude patterns
[ http://jira.codehaus.org/browse/JBEHAVE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-367: - Summary: Add to StoryFinder method to find paths by URL code location and single include/exclude patterns (was: Add StoryFinder.findPaths(URL,String,String)) Add to StoryFinder method to find paths by URL code location and single include/exclude patterns Key: JBEHAVE-367 URL: http://jira.codehaus.org/browse/JBEHAVE-367 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.1 A very common use case is to look up paths using a URL code location. Moreover the single include/exclude pattern is also by far the most used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-368) Ensure same instance of EmbedderClassLoader is used to find and run stories from Ant or Maven
[ http://jira.codehaus.org/browse/JBEHAVE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-368. -- Resolution: Fixed Ensure same instance of EmbedderClassLoader is used to find and run stories from Ant or Maven - Key: JBEHAVE-368 URL: http://jira.codehaus.org/browse/JBEHAVE-368 Project: JBehave Issue Type: Bug Components: Ant Tasks, Maven Plugin Affects Versions: 3.0.2 Environment: Maven 2.2.1 and JDK 1.6 Reporter: Daniel Godfrey Assignee: Mauro Talevi Fix For: 3.1 Attachments: jb.patch I'm getting the following stacktrace when using the ServiceLoader infrastructure in my JBehave steps while running under the maven plugin. I think this is caused by using different class loaders to find the stories and then to execute them. It starts working if I patch createClassLoader in AbstractEmbedderMojo to cache the created classloader and to reuse that every time. java.lang.ClassCastException at java.lang.Class.cast(Class.java:2990) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:345) at java.util.ServiceLoader$1.next(ServiceLoader.java:421) at com.salerio.idm.service.AdaptorsModule.configure(AdaptorsModule.java:33) at com.google.inject.AbstractModule.configure(AbstractModule.java:59) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223) at com.google.inject.spi.Elements.getElements(Elements.java:101) at com.google.inject.InjectorShell$Builder.build(InjectorShell.java:135) at com.google.inject.InjectorBuilder.build(InjectorBuilder.java:102) at com.google.inject.Guice.createInjector(Guice.java:92) at com.google.inject.Guice.createInjector(Guice.java:69) at functional.BaseFixture.initializeInjector(BaseFixture.java:272) at functional.BaseFixture.initialize(BaseFixture.java:104) at bdd.FixedIncomeSteps.init(FixedIncomeSteps.java:36) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jbehave.core.steps.StepCreator$BeforeOrAfter.run(StepCreator.java:348) at org.jbehave.core.steps.StepCreator$1.perform(StepCreator.java:74) at org.jbehave.core.embedder.StoryRunner$FineSoFar.run(StoryRunner.java:202) at org.jbehave.core.embedder.StoryRunner.runSteps(StoryRunner.java:187) at org.jbehave.core.embedder.StoryRunner.runStorySteps(StoryRunner.java:170) at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:84) at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:63) at org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:194) at bdd.MyStories.run(MyStories.java:52) at org.jbehave.core.embedder.Embedder.runStoriesWithAnnotatedEmbedderRunner(Embedder.java:137) at org.jbehave.mojo.RunStoriesWithAnnotatedEmbedderRunner.execute(RunStoriesWithAnnotatedEmbedderRunner.java:20) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at
[jbehave-dev] [jira] Resolved: (JBEHAVE-366) Upgrade to use SyntaxHighlighter 3 for reports
[ http://jira.codehaus.org/browse/JBEHAVE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-366. -- Resolution: Fixed SH 3.0.83 now comes bundled with jbehave-site-resources-3.1. Upgrade to use SyntaxHighlighter 3 for reports -- Key: JBEHAVE-366 URL: http://jira.codehaus.org/browse/JBEHAVE-366 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.1 Amongst other things it does not use Flash and IE would stop winging. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-361) Add configurable sorting strategies for stories in reports
[ http://jira.codehaus.org/browse/JBEHAVE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-361: - Fix Version/s: (was: 3.1) 3.2 Add configurable sorting strategies for stories in reports -- Key: JBEHAVE-361 URL: http://jira.codehaus.org/browse/JBEHAVE-361 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.2 Allow stories to be sorted by different configurable strategies: - alphabetical - by success/failure criteria - by number of scenarios or steps -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Commented: (JBEHAVE-368) Ensure same instance of EmbedderClassLoader is used to find and run stories from Ant or Maven
[ http://jira.codehaus.org/browse/JBEHAVE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=240257#action_240257 ] Mauro Talevi commented on JBEHAVE-368: -- Daniel, fix in 3.1-beta-2. Could you please try it out and let us know if it works on your build? Ensure same instance of EmbedderClassLoader is used to find and run stories from Ant or Maven - Key: JBEHAVE-368 URL: http://jira.codehaus.org/browse/JBEHAVE-368 Project: JBehave Issue Type: Bug Components: Ant Tasks, Maven Plugin Affects Versions: 3.0.2 Environment: Maven 2.2.1 and JDK 1.6 Reporter: Daniel Godfrey Assignee: Mauro Talevi Fix For: 3.1 Attachments: jb.patch I'm getting the following stacktrace when using the ServiceLoader infrastructure in my JBehave steps while running under the maven plugin. I think this is caused by using different class loaders to find the stories and then to execute them. It starts working if I patch createClassLoader in AbstractEmbedderMojo to cache the created classloader and to reuse that every time. java.lang.ClassCastException at java.lang.Class.cast(Class.java:2990) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:345) at java.util.ServiceLoader$1.next(ServiceLoader.java:421) at com.salerio.idm.service.AdaptorsModule.configure(AdaptorsModule.java:33) at com.google.inject.AbstractModule.configure(AbstractModule.java:59) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223) at com.google.inject.spi.Elements.getElements(Elements.java:101) at com.google.inject.InjectorShell$Builder.build(InjectorShell.java:135) at com.google.inject.InjectorBuilder.build(InjectorBuilder.java:102) at com.google.inject.Guice.createInjector(Guice.java:92) at com.google.inject.Guice.createInjector(Guice.java:69) at functional.BaseFixture.initializeInjector(BaseFixture.java:272) at functional.BaseFixture.initialize(BaseFixture.java:104) at bdd.FixedIncomeSteps.init(FixedIncomeSteps.java:36) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jbehave.core.steps.StepCreator$BeforeOrAfter.run(StepCreator.java:348) at org.jbehave.core.steps.StepCreator$1.perform(StepCreator.java:74) at org.jbehave.core.embedder.StoryRunner$FineSoFar.run(StoryRunner.java:202) at org.jbehave.core.embedder.StoryRunner.runSteps(StoryRunner.java:187) at org.jbehave.core.embedder.StoryRunner.runStorySteps(StoryRunner.java:170) at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:84) at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:63) at org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:194) at bdd.MyStories.run(MyStories.java:52) at org.jbehave.core.embedder.Embedder.runStoriesWithAnnotatedEmbedderRunner(Embedder.java:137) at org.jbehave.mojo.RunStoriesWithAnnotatedEmbedderRunner.execute(RunStoriesWithAnnotatedEmbedderRunner.java:20) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
[jbehave-dev] [jira] Updated: (JBEHAVE-364) Order-preserving ExamplesTable
[ http://jira.codehaus.org/browse/JBEHAVE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-364: - Fix Version/s: 3.1 Order-preserving ExamplesTable -- Key: JBEHAVE-364 URL: http://jira.codehaus.org/browse/JBEHAVE-364 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.1 Currently the ExampleTable does not guarantee order of the columns since the row is returned as a Map. In some cases, the preserving the order of the textual table may be useful in the implementation of the step. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-369) Allow processing of system processing before stories are run
Allow processing of system processing before stories are run Key: JBEHAVE-369 URL: http://jira.codehaus.org/browse/JBEHAVE-369 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.1 Some systems used to implement steps may use system properties to control or override their behaviour. E.g. WebDriver system properties to override the default location of the browsers. While system properties may be set at command-line via -D parameters, it is useful to be able to set them via the Embedder and set them before the stories are run. The system properties should also be configurable via Ant or Maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Commented: (JBEHAVE-371) Leading and trailing spaces in example table cells are removed
[
http://jira.codehaus.org/browse/JBEHAVE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=240320#action_240320
]
Mauro Talevi commented on JBEHAVE-371:
--
Frank, what's the use case for keeping the spaces?
Leading and trailing spaces in example table cells are removed
--
Key: JBEHAVE-371
URL: http://jira.codehaus.org/browse/JBEHAVE-371
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.0.3
Reporter: Frank Grimm
Priority: Minor
In JBehave Core 3.0.3 all leading and trailing spaces are removed from
example table cells.
For example, when accessed through the ExamplesTable API (the following table
{code}
| |A | B | C|
| |X | Y | Z|
{code}
becomes
{code}
||A|B|C|
||X|Y|Z|
{code}
Leading/trailing spaces were not removed for JBehave Core versions older than
3.0.3. So, it might be a regression cause when this
http://jira.codehaus.org/browse/JBEHAVE-353 was fixed.
At least for me it would be nice to be able to use example tables containing
cells with leading/trailing spaces.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Commented: (JBEHAVE-371) Leading and trailing spaces in example table cells are removed
[
http://jira.codehaus.org/browse/JBEHAVE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=240335#action_240335
]
Mauro Talevi commented on JBEHAVE-371:
--
It's actually trivial to not trim the table cells, but the real point is that
most users would find that less useful or annoying to have to trim it
themselves. We need to find a way to support multiple parsing modes, whist
using the same parser (the ExamplesTable model class).
Some optional parsing meta info before the table data might do the trick,
identified as anything in [] before first header separator. E.g.:
{code}
[trim=false]
| |A | B | C|
| |X | Y | Z|
{code}
Then we could also add other directives, e.g. for the default sorting of the
data.
Leading and trailing spaces in example table cells are removed
--
Key: JBEHAVE-371
URL: http://jira.codehaus.org/browse/JBEHAVE-371
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.0.3
Reporter: Frank Grimm
Priority: Minor
In JBehave Core 3.0.3 all leading and trailing spaces are removed from
example table cells.
For example, when accessed through the ExamplesTable API (the following table
{code}
| |A | B | C|
| |X | Y | Z|
{code}
becomes
{code}
||A|B|C|
||X|Y|Z|
{code}
Leading/trailing spaces were not removed for JBehave Core versions older than
3.0.3. So, it might be a regression cause when this
http://jira.codehaus.org/browse/JBEHAVE-353 was fixed.
At least for me it would be nice to be able to use example tables containing
cells with leading/trailing spaces.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-364) Ensure ExamplesTable preserves ordering of columns
[ http://jira.codehaus.org/browse/JBEHAVE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-364. -- Resolution: Fixed Ensure ExamplesTable preserves ordering of columns -- Key: JBEHAVE-364 URL: http://jira.codehaus.org/browse/JBEHAVE-364 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.1 Currently the ExampleTable does not guarantee order of the columns since the row is returned as a HashMap. In some cases, the preserving the order of the textual table may be useful in the implementation of the step. Using LinkedHashMap would preserve the ordering, at a small cost of performance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-364) Ensure ExamplesTable preserves ordering of columns
[ http://jira.codehaus.org/browse/JBEHAVE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-364: - Description: Currently the ExampleTable does not guarantee order of the columns since the row is returned as a HashMap. In some cases, the preserving the order of the textual table may be useful in the implementation of the step. Using LinkedHashMap would preserve the ordering, at a small cost of performance. was: Currently the ExampleTable does not guarantee order of the columns since the row is returned as a Map. In some cases, the preserving the order of the textual table may be useful in the implementation of the step. Summary: Ensure ExamplesTable preserves ordering of columns (was: Order-preserving ExamplesTable) Ensure ExamplesTable preserves ordering of columns -- Key: JBEHAVE-364 URL: http://jira.codehaus.org/browse/JBEHAVE-364 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.1 Currently the ExampleTable does not guarantee order of the columns since the row is returned as a HashMap. In some cases, the preserving the order of the textual table may be useful in the implementation of the step. Using LinkedHashMap would preserve the ordering, at a small cost of performance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-369) Allow processing of system processing before stories are run
[ http://jira.codehaus.org/browse/JBEHAVE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-369. -- Resolution: Fixed Allow processing of system processing before stories are run Key: JBEHAVE-369 URL: http://jira.codehaus.org/browse/JBEHAVE-369 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.1 Some systems used to implement steps may use system properties to control or override their behaviour. E.g. WebDriver system properties to override the default location of the browsers. While system properties may be set at command-line via -D parameters, it is useful to be able to set them via the Embedder and set them before the stories are run. The system properties should also be configurable via Ant or Maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-369) Allow processing of system properties before stories are run
[ http://jira.codehaus.org/browse/JBEHAVE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-369: - Summary: Allow processing of system properties before stories are run (was: Allow processing of system processing before stories are run) Allow processing of system properties before stories are run Key: JBEHAVE-369 URL: http://jira.codehaus.org/browse/JBEHAVE-369 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.1 Some systems used to implement steps may use system properties to control or override their behaviour. E.g. WebDriver system properties to override the default location of the browsers. While system properties may be set at command-line via -D parameters, it is useful to be able to set them via the Embedder and set them before the stories are run. The system properties should also be configurable via Ant or Maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Resolved: (JBEHAVE-371) Leading and trailing spaces in example table cells are removed
[
http://jira.codehaus.org/browse/JBEHAVE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-371.
--
Resolution: Fixed
Leading and trailing spaces in example table cells are removed
--
Key: JBEHAVE-371
URL: http://jira.codehaus.org/browse/JBEHAVE-371
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.0.3
Reporter: Frank Grimm
Priority: Minor
In JBehave Core 3.0.3 all leading and trailing spaces are removed from
example table cells.
For example, when accessed through the ExamplesTable API (the following table
{code}
| |A | B | C|
| |X | Y | Z|
{code}
becomes
{code}
||A|B|C|
||X|Y|Z|
{code}
Leading/trailing spaces were not removed for JBehave Core versions older than
3.0.3. So, it might be a regression cause when this
http://jira.codehaus.org/browse/JBEHAVE-353 was fixed.
At least for me it would be nice to be able to use example tables containing
cells with leading/trailing spaces.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Updated: (JBEHAVE-371) Allow leading and trailing spaces to be preserved in example table cells
[
http://jira.codehaus.org/browse/JBEHAVE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-371:
-
Issue Type: Improvement (was: Bug)
Summary: Allow leading and trailing spaces to be preserved in example
table cells (was: Leading and trailing spaces in example table cells are
removed)
Allow leading and trailing spaces to be preserved in example table cells
Key: JBEHAVE-371
URL: http://jira.codehaus.org/browse/JBEHAVE-371
Project: JBehave
Issue Type: Improvement
Components: Core
Affects Versions: 3.0.3
Reporter: Frank Grimm
Assignee: Mauro Talevi
Priority: Minor
Fix For: 3.1
In JBehave Core 3.0.3 all leading and trailing spaces are removed from
example table cells.
For example, when accessed through the ExamplesTable API (the following table
{code}
| |A | B | C|
| |X | Y | Z|
{code}
becomes
{code}
||A|B|C|
||X|Y|Z|
{code}
Leading/trailing spaces were not removed for JBehave Core versions older than
3.0.3. So, it might be a regression cause when this
http://jira.codehaus.org/browse/JBEHAVE-353 was fixed.
At least for me it would be nice to be able to use example tables containing
cells with leading/trailing spaces.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Created: (JBEHAVE-372) Parametrised GivenStories
Parametrised GivenStories
-
Key: JBEHAVE-372
URL: http://jira.codehaus.org/browse/JBEHAVE-372
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Fix For: 3.1
GivenStories could be parametrised, using the same mechanism of the
ExamplesTable and the named parameters.
If a GivenStory path has an anchor with a number, e.g.
GivenStories: /path/to/precondition.story#{0}
then the number is assumed to be the row of the ExamplesTable containing the
required parameters (if present).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Work started: (JBEHAVE-372) Parametrised GivenStories
[
http://jira.codehaus.org/browse/JBEHAVE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JBEHAVE-372 started by Mauro Talevi.
Parametrised GivenStories
-
Key: JBEHAVE-372
URL: http://jira.codehaus.org/browse/JBEHAVE-372
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Fix For: 3.1
GivenStories could be parametrised, using the same mechanism of the
ExamplesTable and the named parameters.
If a GivenStory path has an anchor with a number, e.g.
GivenStories: /path/to/precondition.story#{0}
then the number is assumed to be the row of the ExamplesTable containing the
required parameters (if present).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Commented: (JBEHAVE-372) Parametrised GivenStories
[
http://jira.codehaus.org/browse/JBEHAVE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=240587#action_240587
]
Mauro Talevi commented on JBEHAVE-372:
--
Any sequence of scenarios containing parametrised steps, using exactly the same
mechanism in play with the Examples. E.g.
{code}
GivenStories: org/jbehave/examples/trader/stories/parametrised.story#{0}
When the stock is traded at price 1.1
Then the alert status is ON
Examples:
|symbol|threshold|
|STK1 |1.0|
{code}
where the parametrised story might look like:
{code}
Scenario:
Given a stock of symbol and a threshold
{code}
The parameters are picked up from the table row specified in the anchor. So
we now have parametrised GivenStories, in addition to the parametrised
Scenarios we've always had.
Note that since the Examples table is used to provide data to the GivenStories,
it is not being used to parametrise at the same time the scenario itself (it
looks for the presence of anchors in the GivenStories paths). Nothing
technically stopping us from using the examples table in parametrising both the
GivenStories and the scenario itself, but it'd most probably lead to confusion.
We could use the new feature of ExamplesTable (JBEHAVE-371) to pass in some
directive, e.g.:
{code}
{scope=Scenario}
Examples:
|symbol|threshold|
|STK1 |1.0|
{code}
But that's probably another story ...
Parametrised GivenStories
-
Key: JBEHAVE-372
URL: http://jira.codehaus.org/browse/JBEHAVE-372
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Fix For: 3.1
GivenStories could be parametrised, using the same mechanism of the
ExamplesTable and the named parameters.
If a GivenStory path has an anchor with a number, e.g.
GivenStories: /path/to/precondition.story#{0}
then the number is assumed to be the row of the ExamplesTable containing the
required parameters (if present).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-372) Parametrised GivenStories
[
http://jira.codehaus.org/browse/JBEHAVE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=240587#action_240587
]
Mauro Talevi edited comment on JBEHAVE-372 at 10/22/10 4:32 AM:
Any sequence of scenarios containing parametrised steps, using exactly the same
mechanism in play with the Examples. E.g.
{code}
GivenStories: org/jbehave/examples/trader/stories/parametrised.story#{0}
When the stock is traded at price 1.1
Then the alert status is ON
Examples:
|symbol|threshold|
|STK1 |1.0|
{code}
where the parametrised story might look like:
{code}
Scenario:
Given a stock of symbol and a threshold
{code}
The parameters are picked up from the table row specified in the anchor. So
we now have parametrised GivenStories, in addition to the parametrised
Scenarios we've always had.
Note that since the Examples table is used to provide data to the GivenStories,
it is not being used to parametrise at the same time the scenario itself (it
looks for the presence of anchors in the GivenStories paths). Nothing
technically stopping us from using the examples table in parametrising both the
GivenStories and the scenario itself, but it'd most probably lead to confusion.
We could use the new feature of ExamplesTable (JBEHAVE-371) to pass in some
directive, e.g.:
{code}
Examples:
{scope=Scenario}
|symbol|threshold|
|STK1 |1.0|
{code}
But that's probably another story ...
was (Author: maurotalevi):
Any sequence of scenarios containing parametrised steps, using exactly the
same mechanism in play with the Examples. E.g.
{code}
GivenStories: org/jbehave/examples/trader/stories/parametrised.story#{0}
When the stock is traded at price 1.1
Then the alert status is ON
Examples:
|symbol|threshold|
|STK1 |1.0|
{code}
where the parametrised story might look like:
{code}
Scenario:
Given a stock of symbol and a threshold
{code}
The parameters are picked up from the table row specified in the anchor. So
we now have parametrised GivenStories, in addition to the parametrised
Scenarios we've always had.
Note that since the Examples table is used to provide data to the GivenStories,
it is not being used to parametrise at the same time the scenario itself (it
looks for the presence of anchors in the GivenStories paths). Nothing
technically stopping us from using the examples table in parametrising both the
GivenStories and the scenario itself, but it'd most probably lead to confusion.
We could use the new feature of ExamplesTable (JBEHAVE-371) to pass in some
directive, e.g.:
{code}
{scope=Scenario}
Examples:
|symbol|threshold|
|STK1 |1.0|
{code}
But that's probably another story ...
Parametrised GivenStories
-
Key: JBEHAVE-372
URL: http://jira.codehaus.org/browse/JBEHAVE-372
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Fix For: 3.1
GivenStories could be parametrised, using the same mechanism of the
ExamplesTable and the named parameters.
If a GivenStory path has an anchor with a number, e.g.
GivenStories: /path/to/precondition.story#{0}
then the number is assumed to be the row of the ExamplesTable containing the
required parameters (if present).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
