The issue of the report generation was the lack of log4j dependency at
the maven plugin level: http://jbehave.org/reference/stable/maven-goals.html
As for the expected behaviour, do note that the story timeout is global,
i.e. not per effective story execution time, in the sense that it's
calculated (in "real" time) from the moment the execution of all stories
starts. After the elapsed time as reached the timeout, all story
execution is cancelled. We can try to improve on this for 4.0.
I was able to run the stories and the cycling story does indeed hang but
that's by design, as I understand it. Note that the threads = 1 in the
pom.xml. I was able to complete the other stories by using 2 or 3 threads.
Cheers
On 08/09/2012 12:05, Alexander Lehmann wrote:
I have changed a few bits in the project to make it run with the main
maven repository versions and changed the search page to a dummy page
(which essentially hangs when you enter cycling to simulate the timeout)
When I now run the stories, the first story reaches the timeout and
everything after that isn't executed including the report generation.
Also I noticed that it keeps the Firefox open even though the maven
script is finished.
I think that is not the expected behavior, it should create the
reports even on timeout. I will look a bit into why that happens,
maybe this is a problem in exception handling?
On 07.09.2012 12:55, mary walshe wrote:
I have attached a small project which has the same configuration as my
own project that reproduces the issue.
Cheers,
Mary
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
