Thank you very much. It works now with my example.
On Wed, Jun 18, 2014 at 6:39 PM, Mauro Talevi mauro.tal...@aquilonia.org
wrote:
4.0-beta-8 has just been released, with the agreed keywords.
On 18/06/2014 08:55, Hans Schwäbli wrote:
When will there be a beta-8 version of the 4.x branch
4.0-beta-8 has just been released, with the agreed keywords.
On 18/06/2014 08:55, Hans Schwäbli wrote:
When will there be a beta-8 version of the 4.x branch containing this fix?
I am asking because the examples for the JBehave article will need
that, and the magazine is published on 2nd of
Sold! To the German-speaking gentleman at the back of the room :-)
On 20/05/2014 21:00, Mirko Friedenhagen wrote:
Hans,
I stand corrected, in this case JEDES is a better translation for ANY.
And make FAILURE FEHLER.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
So, what's the consensus then with the keywords?
On 16/05/2014 18:42, Mauro Talevi wrote:
I'll defer to whatever you guys decide is best. We can always change
it later.
On 15/05/2014 18:27, Mirko Friedenhagen wrote:
Hans,
I am not sure I agree :-). JEDES would be EVERY IMO.
According to
I'll defer to whatever you guys decide is best. We can always change it
later.
On 15/05/2014 18:27, Mirko Friedenhagen wrote:
Hans,
I am not sure I agree :-). JEDES would be EVERY IMO.
According to ISTQB FEHLER would be the DEFECT which causes a FAILURE
(FEHLSCHLAG), which may lead to an
I re-tested it and now it works. Thank you!
However I did not use that feature in-depth so there might be some other
isues.
I wondered a bit about outcome ANY. It seems to be like the finally-block
in Java. The German translation IRGENDWELCHE is maybe not the best for ANY.
Ergebnis: BELIEBIGES
Hans,
I am not sure I agree :-). JEDES would be EVERY IMO.
According to ISTQB FEHLER would be the DEFECT which causes a FAILURE
(FEHLSCHLAG), which may lead to an AUSFALL (BREAKDOWN) of a server ;-)
Am 15.05.2014 12:34 schrieb Hans Schwäbli bugs.need.love@gmail.com:
I re-tested it and now
I quickly tested the lifecycle.
Story:
Lebenszyklus:
Vorher:
Gegeben im Lager sind 100 T-Shirts
Nach:
Ergebnis: ERFOLG
Gegeben im Lager sind 200 T-Shirts
Ergebnis: IRGENDWELCHE
Gegeben im Lager sind 300 T-Shirts
Ergebnis: AUSFALL
Gegeben im Lager sind 400 T-Shirts
Szenario: Versandkosten fallen
I mixed up snapshot versions with beta-versions, sorry.
I tried now the snapshot version and it works now as expected concerning
the problem with the examples table.
Thank you!
But there is a problem with comments. I will write a posting just on that.
On Thu, May 8, 2014 at 10:51 AM, Mauro
Cool, we'll push out new beta soon.
Can you also take the Lifecycle After upon outcome functionality for a
spin while you're at it?
On 13/05/2014 13:42, Hans Schwäbli wrote:
I mixed up snapshot versions with beta-versions, sorry.
I tried now the snapshot version and it works now as expected
Thank you! Is it also deployed?
I did not find it here:
https://nexus.codehaus.org/content/groups/public/org/jbehave/jbehave-core/4.0-beta-7/
The last snapshot there is from 2nd of May.
The same snapshot date is on:
http://mvnrepository.com/artifact/org.jbehave/jbehave-maven-plugin/4.0-beta-7/
No, a new beta has not been deployed yet. In the meantime, you can use the
latest 3.9.x or build the 4.0 snapshot from source.
On 8 May 2014, at 08:59, Hans Schwäbli bugs.need.love@gmail.com wrote:
Thank you! Is it also deployed?
I did not find it here:
I committed it here: https://github.com/OttoDiesel/jbehave-shop-example.git
I will add such a scenario to the core examples. Until then you could use
that other example if you like. It is the example for the article on
JBehave by the way.
On Tue, May 6, 2014 at 3:04 PM, Mauro Talevi
I created such an example for jbehave-core now and attached it to this
posting. I still cannot work on a clone the Github project because of
company restrictions (I haven't yet received an answer why it is not
working inside the company proxy).
In case the mailing list does not support
I already use StoryControls.doIgnoreMetaFiltersIfGivenStory(true). And I
removed the given story in the story.
But the result is the same.
Maybe tomorrow I can commit the whole project, so that you can reproduce it.
On Tue, May 6, 2014 at 11:00 AM, Stephen de Vries stephe...@gmail.comwrote:
Yes, it looks likely to be unrelated to given stories and such.
Could you please add a scenario reproducing the behaviour to the
meta_filtering.story in the core examples (preferably in English)?
Does it work with 3.x?
On 06/05/2014 11:34, Hans Schwäbli wrote:
I already use
16 matches
Mail list logo
