[jbehave-dev] [jira] (JBEHAVE-765) Variants documentation is misleading wrt whitespace
[
https://jira.codehaus.org/browse/JBEHAVE-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-765.
--
Resolution: Fixed
Fix Version/s: 3.6.3
> Variants documentation is misleading wrt whitespace
> ---
>
> Key: JBEHAVE-765
> URL: https://jira.codehaus.org/browse/JBEHAVE-765
> Project: JBehave
> Issue Type: Bug
> Components: Documentation
>Affects Versions: 3.6
>Reporter: Daniel Schneller
>Priority: Minor
> Fix For: 3.6.3
>
>
> On the pattern variants documentation page
> http://jbehave.org/reference/stable/pattern-variants.html the example is
> misleading regarding whitespace placement for optional expressions. The
> example currently reads:
> {code}
> @When("the {item|} {price|cost} is $price")
> {code}
> Notice the white space between `{item|}` and `{price|...}`. The intention is
> to show optional parts in the expression. However, in this form leaving out
> the word `item` would require two consecutive spaces for the step to be
> identified (one after "the" and one before "price").
> The example should read:
> {code}
> @When("the {item |}{price|cost} is $price")
> {code}
> and maybe include a note in the text below it:
> Notice that the word "item" becomes effectively optional in this example.
> However, make sure to include the space following it in the variant to
> prevent the resulting step from containing multiple consecutive spaces!
--
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
[jbehave-scm] [scm-core][1] JBEHAVE-765: Clarified variants docs.
commit ac10a91dc0cfd2a98684357f11ab6b8528d4881e
Author: Mauro Talevi
AuthorDate: Tue Apr 17 20:19:39 2012 +0200
Commit: Mauro Talevi
CommitDate: Tue Apr 17 20:19:39 2012 +0200
JBEHAVE-765: Clarified variants docs.
diff --git a/distribution/src/site/content/pattern-variants.html
b/distribution/src/site/content/pattern-variants.html
index 2ddad2a..2e9adfc 100755
--- a/distribution/src/site/content/pattern-variants.html
+++ b/distribution/src/site/content/pattern-variants.html
@@ -23,7 +23,7 @@ When the price is 10.0
When the cost is 10.0
-then we could define two aliases, but it's simpler and more compact to
write a pattern with variants:
+then we could define two aliases, but it's simpler and more compact to
write a pattern with variants. E.g.:
@When("the {item|} {price|cost} is $price")
public void theItemPriceIs(double price) {
@@ -31,6 +31,9 @@ When the cost is 10.0
}
+In this example, we want the word "item" to be optional. Please note that
we include a trailing space in the variant "{item |}"
+and not between this and the following variant ("{price|cost}") to prevent the
resulting step from containing multiple consecutive spaces.
+
The pattern variants are built by the PatternVariantBuilder,
which interprets the directives of the form:
[jbehave-dev] [jira] (JBEHAVE-766) Documentation to configure maven-plugin should be updated
[ https://jira.codehaus.org/browse/JBEHAVE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296655#comment-296655 ] Mauro Talevi commented on JBEHAVE-766: -- Hi Anders, I think there is some confusion around what is a "test". In Maven, target/test-classes is where the unit test classes would reside, but not necessarily the integration tests. By default, JBehave assumes that you are running integration tests and in a separate bespoke module (because it typically these have a cross-modular and cross-cutting concern). The Maven properties in http://jbehave.org/reference/stable/maven-goals.html does include the property and it says it defaults to "compile". Hence the plugin does not worry about the surefire properties, e.g. -DskipTests. Of course, you can configure to JBehave stories as JUnit tests, e.g. via the surefire plugin, but it's separate from the JBehave Maven plugin. That said, we can certainly improve the docs to explain and clarify this. > 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 > test 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
[jbehave-dev] [jira] (JBEHAVE-767) Norwegian language support out-of-the-box
[ https://jira.codehaus.org/browse/JBEHAVE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-767. -- Resolution: Fixed Added Norwegian keywords with thanks. > 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 >Reporter: Anders Sandberg Nordbø >Priority: Minor > Fix For: 3.6.3 > > Attachments: keywords_no.properties > > > 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
[jbehave-scm] [scm-core][1] JBEHAVE-767: Added keywords_no.properties, contributed by Anders Sandberg Nordbø.
commit 958187acbc02c7ef9a0cd851ea7a30225bac145a
Author: Mauro Talevi
AuthorDate: Tue Apr 17 18:37:18 2012 +0200
Commit: Mauro Talevi
CommitDate: Tue Apr 17 18:37:18 2012 +0200
JBEHAVE-767: Added keywords_no.properties, contributed by Anders Sandberg
Nordbø.
diff --git a/jbehave-core/src/main/resources/i18n/keywords_no.properties
b/jbehave-core/src/main/resources/i18n/keywords_no.properties
new file mode 100644
index 000..fc806a1
--- /dev/null
+++ b/jbehave-core/src/main/resources/i18n/keywords_no.properties
@@ -0,0 +1,30 @@
+Meta=Meta:
+MetaProperty=@
+Narrative=Fortelling:
+InOrderTo=For \u00e5
+AsA=Som en
+IWantTo=\u00d8nsker jeg \u00e5
+Scenario=Scenario:
+GivenStories=Gitt stories
+ExamplesTable=Eksempler:
+ExamplesTableRow=Eksempel:
+ExamplesTableHeaderSeparator=|
+ExamplesTableValueSeparator=|
+ExamplesTableIgnorableSeparator=|--
+Given=Gitt
+When=N\u00e5r
+Then=S\u00e5
+And=Og
+Ignorable=!--
+Pending=AVVENTER
+NotPerformed=IKKE UTF\u00d8RT
+Failed=FEILET
+DryRun=TESTKJ\u00d8RING
+StoryCancelled=STORY AVBRUTT
+Duration=VARIGHET
+OutcomeDescription=Beskrivelse
+OutcomeValue=Verdi
+OutcomeMatcher=Matcher
+OutcomeVerified=Verifisert
+Yes=Ja
+No=Nei
diff --git
a/jbehave-core/src/test/java/org/jbehave/core/i18n/LocalizedKeywordsBehaviour.java
b/jbehave-core/src/test/java/org/jbehave/core/i18n/LocalizedKeywordsBehaviour.java
index 8ddb247..cbd27cc 100755
---
a/jbehave-core/src/test/java/org/jbehave/core/i18n/LocalizedKeywordsBehaviour.java
+++
b/jbehave-core/src/test/java/org/jbehave/core/i18n/LocalizedKeywordsBehaviour.java
@@ -52,6 +52,7 @@ public class LocalizedKeywordsBehaviour {
ensureKeywordsAreLocalisedFor(new Locale("en"));
ensureKeywordsAreLocalisedFor(new Locale("fr"));
ensureKeywordsAreLocalisedFor(new Locale("it"));
+ensureKeywordsAreLocalisedFor(new Locale("no"));
ensureKeywordsAreLocalisedFor(new Locale("pt"));
ensureKeywordsAreLocalisedFor(new Locale("tr"));
ensureKeywordsAreLocalisedFor(new Locale("zh_TW"));
[jbehave-dev] [jira] (JBEHAVE-767) Norwegian language support out-of-the-box
[ https://jira.codehaus.org/browse/JBEHAVE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-767: - Affects Version/s: (was: 3.6.2) 3.6 Fix Version/s: 3.6.3 > 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 >Reporter: Anders Sandberg Nordbø >Priority: Minor > Fix For: 3.6.3 > > Attachments: keywords_no.properties > > > 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
[jbehave-dev] [jira] (JBEHAVE-501) Report stying not being generated
[
https://jira.codehaus.org/browse/JBEHAVE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296652#comment-296652
]
Anders Sandberg Nordbø commented on JBEHAVE-501:
I agree this would make it easier, even if this is not a bug it would be
beneficial to move this issue to improvement.
> Report stying not being generated
> -
>
> Key: JBEHAVE-501
> URL: https://jira.codehaus.org/browse/JBEHAVE-501
> Project: JBehave
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.3.2
> Environment: Ant, Eclipse, JDK6
>Reporter: Derek Clarkson
> Fix For: 3.4
>
>
> I am using this report builder definition in a annotation setup as per the
> JBehave website documentation:
> public static class MyReportBuilder extends StoryReporterBuilder {
> public MyReportBuilder() {
> super();
>
> this.withCodeLocation(CodeLocations.codeLocationFromPath("build/publish/x"));
> this.withRelativeDirectory("story-reports");
> this.withDefaultFormats();
> this.withFormats(CONSOLE, HTML);
> }
> }
> The reports are being generated in the view directory, however there are no
> images, css or javascript being generated even though the html refers to
> them. I've scoured the web site documentation which suggests that they should
> be and tells you how to turn them off, but not what to do if they are not
> there.
--
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
[jbehave-dev] [jira] (JBEHAVE-767) Norwegian language support out-of-the-box
[ https://jira.codehaus.org/browse/JBEHAVE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Sandberg Nordbø updated JBEHAVE-767: --- Attachment: keywords_no.properties > 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 > Attachments: keywords_no.properties > > > 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
[jbehave-dev] [jira] (JBEHAVE-767) Norwegian language support out-of-the-box
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
[jbehave-dev] [jira] (JBEHAVE-766) Documentation to configure maven-plugin should be updated
[ https://jira.codehaus.org/browse/JBEHAVE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296639#comment-296639 ] Anders Sandberg Nordbø commented on JBEHAVE-766: When test is not specified, JBehave does not look in target/test-classes where test classes normally would reside. > 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 > test 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
[jbehave-dev] [jira] (JBEHAVE-766) Documentation to configure maven-plugin should be updated
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 test 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
[jbehave-dev] [jira] (JBEHAVE-454) Can't run-stories-as-embeddables from test directory using Maven plugin
[
https://jira.codehaus.org/browse/JBEHAVE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296632#comment-296632
]
Anders Sandberg Nordbø commented on JBEHAVE-454:
FWIW [~estaub], this was helpful to me as well. Thanks for asking - even if
they don't like tickets to be opened, this is searchable info on the web.
Note that the online docs are missing this test from the
configuration and will not work on many projects.
> Can't run-stories-as-embeddables from test directory using Maven plugin
> ---
>
> Key: JBEHAVE-454
> URL: https://jira.codehaus.org/browse/JBEHAVE-454
> Project: JBehave
> Issue Type: Bug
> Components: Maven Plugin
>Affects Versions: 3.1.2
>Reporter: Edward Staub
>
> When I tried to use it, the plugin couldn't find my .java file.
> I suspect that this is because the classloader obtained under Maven with a
> story that uses
> new LoadFromClasspath(this.getClass().getClassLoader())
> as a StoryLoader doesn't include the test class directory - even though the
> running class is IN the test class directory. The same code works correctly
> under the Eclipse debugger (including the test class directory in the
> classpath). Everything else works correctly in Maven - unit tests, etc.
> The configuration:
>
>
> ${project.build.sourceDirectory}
>
> ${project.build.testSourceDirectory}
>
> **/ProcessorTestStory.java
>
>
> +author *
> -skip
>
>
>
> java.awt.headless
> true
>
>
>
> true
> false
>
> -Ed
--
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
[jbehave-dev] [jira] (JBEHAVE-765) Variants documentation is misleading wrt whitespace
Daniel Schneller created JBEHAVE-765:
Summary: Variants documentation is misleading wrt whitespace
Key: JBEHAVE-765
URL: https://jira.codehaus.org/browse/JBEHAVE-765
Project: JBehave
Issue Type: Bug
Components: Documentation
Affects Versions: 3.6
Reporter: Daniel Schneller
Priority: Minor
On the pattern variants documentation page
http://jbehave.org/reference/stable/pattern-variants.html the example is
misleading regarding whitespace placement for optional expressions. The example
currently reads:
{code}
@When("the {item|} {price|cost} is $price")
{code}
Notice the white space between `{item|}` and `{price|...}`. The intention is to
show optional parts in the expression. However, in this form leaving out the
word `item` would require two consecutive spaces for the step to be identified
(one after "the" and one before "price").
The example should read:
{code}
@When("the {item |}{price|cost} is $price")
{code}
and maybe include a note in the text below it:
Notice that the word "item" becomes effectively optional in this example.
However, make sure to include the space following it in the variant to prevent
the resulting step from containing multiple consecutive spaces!
--
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
