http://blog.gmane.org/gmane.comp.java.jbehave.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.java.jbehave.devel/3910 <pre></pre> poulfich (JIRA 2012-05-25T09:21:21 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3908 <pre></pre> jbehaveuser (JIRA 2012-05-24T15:43:21 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3907 <pre></pre> mrJojo (JIRA 2012-05-22T11:22:21 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3904 <pre>David Tanner created JBEHAVE-783: ------------------------------------ Summary: Better integration into JUnit Key: JBEHAVE-783 URL: https://jira.codehaus.org/browse/JBEHAVE-783 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.6.4 Environment: N/A Reporter: David Tanner Priority: Minor Attachments: Configuration change.txt, Improved Test Description.txt, JUnit StoryReporter.txt Problem statement: As has been stated in miscellaneous other Issues, it would be nice to have better integration into JUnit by JBehave. Recommended Code Change: Add two variables to the MostUsefulConfiguration, one to hold RunNotifier, and the other to hold the TestDescriptions. Increase the JUnit Description depth by parsing out the scenarios, and steps when creating the Story descriptions in AnnotatedPathRunner. Add a StoryReporter that reports to the RunNotifier using the provided StoryDescription. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> David Tanner (JIRA 2012-05-16T20:44:02 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3903 <pre>David Tanner created JBEHAVE-782: ------------------------------------ Summary: Minor change to function parseScenario in RegexStoryParser Key: JBEHAVE-782 URL: https://jira.codehaus.org/browse/JBEHAVE-782 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 3.6.4 Environment: N/A Reporter: David Tanner Priority: Trivial Problem Statement: When the RegexStoryParser parses out a scenario, it attempts to remove the title from the step to get the scenario without title, but the function doesn't account for Scenario:\n before the title. I don't think this will affect anything, and I don't think anything was broken initally, I just noticed as debugging that it didn't strip out the actual title because of the Scenario keyword, newline, and space before it. Actual Code: RegexStoryParser line 151: String scenarioWithoutTitle = removeStart(scenarioAsText, title); Recommended Fix: String scenarioWithoutTitle = removeStart(scenarioAsText, keywords.scenario() + "\n " + title); Where "\n " can be replaced with whatever new line character is being used plus the space. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> David Tanner (JIRA 2012-05-16T20:22:02 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3901 <pre>Mauro Talevi created JBEHAVE-781: ------------------------------------ Summary: Deprecate ConfigurableEmbedder addSteps() methods in favour of useStepsFactory() Key: JBEHAVE-781 URL: https://jira.codehaus.org/browse/JBEHAVE-781 Project: JBehave Issue Type: Task Components: Core Reporter: Mauro Talevi Priority: Minor Fix For: 3.6.7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Mauro Talevi (JIRA 2012-05-15T09:48:03 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3899 <pre>prem created JBEHAVE-780: ---------------------------- Summary: Isolate parameter data from .story files Key: JBEHAVE-780 URL: https://jira.codehaus.org/browse/JBEHAVE-780 Project: JBehave Issue Type: Story Components: Core Reporter: prem Would like to segregate data from story file so that maintenance between stories and datas can be easy. For example, Given I log into mail account as user $username with password $password example username xxx password xxx. Would like to keep the example part in one file(.xml or text file) and .story file may not have example part. I want to create a mapping between $username from .story file and the data 'xxx' from .xml/.txt file. When Jbehave executes the scenario in step file, it should able to read the data('xxx') from data file and map to appropriate filed($username). Is this possible in present Jbehave framework? Could help us to do this -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> prem (JIRA 2012-05-11T19:01:03 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3884 <pre>Daniel Schneller created JBEHAVE-779: ---------------------------------------- Summary: Change of ExamplesTableFactory constructor in patch release Key: JBEHAVE-779 URL: https://jira.codehaus.org/browse/JBEHAVE-779 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.6.5, 3.6.4 Reporter: Daniel Schneller Priority: Minor With JBEHAVE-718 the constructor public ExamplesTableFactory(Keywords keywords, ResourceLoader resourceLoader, ParameterConverters parameterConverters) was changed to public ExamplesTableFactory(Keywords keywords, ResourceLoader resourceLoader, ParameterConverters parameterConverters, TableTransformers tableTranformers) when the TableTransformers feature was introduced. This is a backwards incompatible change and should not have been included like that in a patch revision with only the last digit of the version number changed, as it breaks existing code (including mine :)) when going up to the latest 3.6 version. I suggest adding back the original constructor with a sensible default behavior. A pull request on GitHub will be sent: https://github.com/jbehave/jbehave-core/pull/31 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Daniel Schneller (JIRA 2012-05-09T21:17:02 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3882 <pre>prem created JBEHAVE-778: ---------------------------- Summary: Capture the execution time of step method in jbehave Key: JBEHAVE-778 URL: https://jira.codehaus.org/browse/JBEHAVE-778 Project: JBehave Issue Type: Story Components: Spring Support Reporter: prem To create an annotation to capture the performance timing of step's method in Jbehave framework. Below is the sample snippet for &lt; at &gt;Profiled annotation. After execution of the below method, should able to log the method execution timing details. &lt; at &gt;Given("I log into mail account as user &lt;username&gt; with password &lt;password&gt;") &lt; at &gt;Profiled public void login(){ .... } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> prem (JIRA 2012-05-09T11:57:02 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3878 <pre>Mauro Talevi created JBEHAVE-777: ------------------------------------ Summary: A tree-based story runner that separates creation of performable steps from execution Key: JBEHAVE-777 URL: https://jira.codehaus.org/browse/JBEHAVE-777 Project: JBehave Issue Type: New Feature Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 4.x In 3.x the StoryRunner creates and executes the steps for each story and scenario while keeping state. We want to separate the creation of performable steps from their execution and build a tree of performable objects. The state should not be held any more as a member variable but in a shared run context. The result of execution of the performable tree should be serialisable and consumable by any reporting/UI layer independent of the StoryReporters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Mauro Talevi (JIRA 2012-05-08T14:32:03 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3877 <pre>Mauro Talevi created JBEHAVE-776: ------------------------------------ Summary: StoryManager should be responsible for running before and after stories steps Key: JBEHAVE-776 URL: https://jira.codehaus.org/browse/JBEHAVE-776 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.6.5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Mauro Talevi (JIRA 2012-04-29T13:44:02 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3874 <pre>Mauro Talevi created JBEHAVE-775: ------------------------------------ Summary: Update web archetypes to be in sync with tutorials Key: JBEHAVE-775 URL: https://jira.codehaus.org/browse/JBEHAVE-775 Project: JBehave Issue Type: Improvement Components: Archetypes Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: web-3.5.3, web-3.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Mauro Talevi (JIRA 2012-04-29T13:13:02 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3868 <pre>Mauro Talevi created JBEHAVE-774: ------------------------------------ Summary: Embedder should pass meta filter to CrossReference Key: JBEHAVE-774 URL: https://jira.codehaus.org/browse/JBEHAVE-774 Project: JBehave Issue Type: Improvement Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.6.5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Mauro Talevi (JIRA 2012-04-29T09:51:02 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3867 <pre>Mauro Talevi created JBEHAVE-773: ------------------------------------ Summary: CrossReference does not consider pending steps as failures when the PendingStepStrategy is used Key: JBEHAVE-773 URL: https://jira.codehaus.org/browse/JBEHAVE-773 Project: JBehave Issue Type: Bug Reporter: Mauro Talevi Assignee: Paul Hammant Fix For: 3.6.5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Mauro Talevi (JIRA 2012-04-29T08:40:02 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3862 <pre>Mauro Talevi created JBEHAVE-772: ------------------------------------ Summary: The web archetypes should be in sync with the tutorials Key: JBEHAVE-772 URL: https://jira.codehaus.org/browse/JBEHAVE-772 Project: JBehave Issue Type: Task Components: Archetypes Reporter: Mauro Talevi Assignee: Mauro Talevi Archetypes are a useful way to get projects started. Having them in sync with tutorials is even more useful. To this end: 1. Make the tutorials standalone from a Maven point of view - even if at a cost of a small redundancy of configuration. This also helps newcomers. 2. Have a script that uses the Maven archetype:create-from-project to generate an archetype from the tutorials and update the archetype source. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Mauro Talevi (JIRA 2012-04-28T16:08:03 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3860 <pre>Paul Hammant created JBEHAVE-771: ------------------------------------ Summary: Upgrade to Selenium 2.21 Key: JBEHAVE-771 URL: https://jira.codehaus.org/browse/JBEHAVE-771 Project: JBehave Issue Type: Task Reporter: Paul Hammant Assignee: Paul Hammant Priority: Minor Fix For: web-3.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Paul Hammant (JIRA 2012-04-28T15:25:12 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3854 <pre>joachim nilsson created JBEHAVE-770: --------------------------------------- Summary: Testcases expects order in result from getMethods() Key: JBEHAVE-770 URL: https://jira.codehaus.org/browse/JBEHAVE-770 Project: JBehave Issue Type: Bug Components: Core Environment: Found the issue using Win7(x64) and Java7u2. Reporter: joachim nilsson Priority: Minor Attachments: 0001-testcase-bugfix-Corrected-testcases-that-were-using-.patch Testcases in CompositeStepCandidateBehaviour and StepCandidateBehaviour uses the resulting list from getMethods() and expected results to be in declaration order. According to Javadoc of java.lang.Class.getMethods(): "Returns an array ... The elements in the array returned are not sorted and are not in any particular order..." Correction attached, making use of an extraction method to find the desired CandidateStep in the test. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> joachim nilsson (JIRA 2012-04-25T23:15:02 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3853 <pre>joachim nilsson created JBEHAVE-769: --------------------------------------- Summary: Swedish language support Key: JBEHAVE-769 URL: https://jira.codehaus.org/browse/JBEHAVE-769 Project: JBehave Issue Type: Improvement Reporter: joachim nilsson Priority: Minor Attachments: keywords_se.properties Swedish language file attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> joachim nilsson (JIRA 2012-04-25T20:39:02 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3851 <pre>Mauro Talevi created JBEHAVE-768: ------------------------------------ Summary: Add documentation page on how to contribute Key: JBEHAVE-768 URL: https://jira.codehaus.org/browse/JBEHAVE-768 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.6.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Mauro Talevi (JIRA 2012-04-25T12:05:03 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3835 <pre>Anders Sandberg Nordbø created JBEHAVE-767: ---------------------------------------------- Summary: Norwegian language support out-of-the-box Key: JBEHAVE-767 URL: https://jira.codehaus.org/browse/JBEHAVE-767 Project: JBehave Issue Type: Improvement Affects Versions: 3.6.2 Reporter: Anders Sandberg Nordbø Priority: Minor I've added a property file here in ANSI encoding with unix line endings and escaped unicode characters as requested. BTW - would be cool if you linked to this tool which does the conversion smoothly: http://www.htmlescape.net/javaescape_tool.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Anders Sandberg Nordbø (JIRA 2012-04-17T15:50:03 http://comments.gmane.org/gmane.comp.java.jbehave.devel/3833 <pre>Anders Sandberg Nordbø created JBEHAVE-766: ---------------------------------------------- Summary: Documentation to configure maven-plugin should be updated Key: JBEHAVE-766 URL: https://jira.codehaus.org/browse/JBEHAVE-766 Project: JBehave Issue Type: Improvement Components: Documentation Affects Versions: 3.6.2 Reporter: Anders Sandberg Nordbø Priority: Minor When introducing JBehave into our project I've run into some challenges - luckily most have been searchable and resolved. We have to separate tests in pom.xml, and the docs does not say &lt;scope&gt;test&lt;/scope&gt; in the plugin configuration, which makes it harder to get started using JBehave for some projects. We also need to be able to run without tests, and use the standard maven flag -DskipTests - the maven plugin docs does not mention how to get this right, but this worked for us: http://stackoverflow.com/questions/7926723/jbehave-maven-how-to-skip-scenario-tests -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email </pre> Anders Sandberg Nordbø (JIRA 2012-04-17T14:16:04 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.java.jbehave.devel