,
Ayesha
--
Alexander Lehmann alexl...@gmail.com
http://about.me/alexlehm
for the change in the in progress version, i usually look at the github
commit list, most of the commits should have the issue number and the
description
(just look for [maven-release-plugin] prepare release ... to find your
current version
I noticed this problem a while back (see
https://jira.codehaus.org/browse/JBEHAVE-800 for 3.6.8), but I think we
decided that this is not easy to change. You can work around the problem
by using 2 different methods, one for the table step and one for the
literal step.
OTOH, if this worked
I haven't used much of the features inside the IDE except running all
the tests together during deployment (however I have a bit of a
different use case for jbehave), I assume the junit notifier feature
should work in different IDEs, since it is not directly a feature of the
IDE (haven't
jbehave doesn't support reporting details to the junit view in the ide,
there is however an additional project that adds a details view
https://github.com/codecentric/jbehave-junit-runner , maybe you can try that
(I think this will not work when you already have a @RunWith annotation)
On
Looks like the project doesn't compile with java 6 (works with java 7)
On 02.12.2012 14:38, Mauro Talevi wrote:
Hi Roy,
your project does not compile:
Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project
the spring-java archtype from jbehave-web has all source files two, once
as packagename.* and once as packagename.esty.*
I wonder if the files were moved at some point and the old files were
not deleted.
-
To unsubscribe
thats what I meant by changing the table separator, if you change the
comment from |-- to e.g. !--, it should work:
Given eclipse
Then the vmarg should be vmarg
Examples:
{ignorableSeparator=!--}
|vmarg|
|--launcher.appendVMargs|
|-Xms512m|
|-Xmx768m|
On 09.11.2012 01:17, Pascal Rapicault
I don't think there is an escape character, you can redefine the table
separator chars though, that should solve the problem. (unless I
misunderstood what you need to, can you post an example then?)
On 08.11.2012 23:26, Pascal Rapicault wrote:
Hello,
In an example table one value that I need
=./src
destdir=CompiledClasses
classpath refid=class.path /
/javac
/target
path id=class.path
fileset dir=C:\jbehave-web-3.5.4\lib
include name=**/*.jar /
/fileset
/path
/project
On Tue, Oct 23, 2012 at 3:40 PM, Alexander Lehmann
alexl...@gmail.com
try running your tests with external Maven in Eclipse, that should
decouple the test from the Eclipse libraries
On 23.10.2012 22:03, Gopu Shrestha wrote:
I am close to develop this POC for my incoming project.
Can any one advise me another alternative ? like using Ant to execute
the test?
On
the FirefoxWebDriverProvider can be exchanged for the
RemoteWebDriverProvider, which supports setting capabilities, but I'm
not quite sure how to do that with Spring (you can probably subclass the
RemoteDriver and change the initialization, not sure if that is a smart
way to do it)
other than
sorry, I had a problem with the GMANE NNTP that posted this a few times
by accident.
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
jbehave can create reports with Freemarker templates, this way you can
substitute the standard report with your own version. Getting the date
should be something like new Date().toString(), not sure how to get the
hostname in freemarker, maybe you can access the shell environment variables
I think you have to remove the unpack-view-resources goal from the first
execution (or you have different versions of jbehave in the pom file,
I'm not sure)
On 12.09.2012 11:40, Roy de Kleijn wrote:
It looks now like this:
plugin
I think we need two additional features
- first of all a hook or something similar to be able to finish up when
a story is cancelled, e.g. shutting down selenium or creating a report
that just mentions that the story was cancelled
- 2nd a per story timeout value that applies to each story
I was looking around the source code and I noticed that the stack traces
are cut off to produce easier to read traces after the first embedder junit
or maven surefire entry.
Would it be useful to put ... in the next line for the stack trace (like
e.g. tomcat does I think) or is this obvious to
(StackTraceFormatterNewTest.java:11)
(reflection-invoke)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
On 12.08.2012 16:24, Mauro Talevi wrote:
Example please ...
On 12/08/2012 14:26, Alexander Lehmann wrote:
I was looking around the source code and I noticed
Hi all,
not sure if something like this is already available, I think it would
be helpful to collection solutions or howtos for common tasks for
jbehave (similar to e.g. the wiki articles for Jenkins).
I noticed that someone asked about using the jenkins plugin for jbehave
which I did a
The suggested way to implement web testing steps in to abstract from the
actual web implementation and use steps classes and another set of
classes called page classes, the examples on the reference guide
describe how to do that
http://jbehave.org/reference/web/stable/page-objects.html
If you are using Windows, make sure that you use the correct char
encoding when copying resources in Maven (utf-8 instead of the local
windows locale), if the story files are copied from src to the
target/classes dir, the files may get converted otherwise. This doesn't
happen in the IDE since
It seems that the maven embedder cannot be a groovy file, since that is
not found, if you change it to a java file, it is found at least.
If you rename the file, loading the embedder fails however since the
Runner class doesn't implement Embeddable, you probably need to use
another class as
I should mention that +skip false is probably not what you need, either
-skip true or -skip is usually correct.
On 03.04.2012 19:59, Alves, David wrote:
Does anyone know if metaFilters can be passed on the maven command line
as a System Property?
I have played with this, but cannot get it to
You may be a able to work around the missing before notification by
collecting all log events until the next after step notification and
then flush the collected log events. The first step starts with the
beforeScenario notification, the first successful/failed notification
ends the previous
If you are using Jenkins or Hudson, you can use the xunit-jbehave plugin
that will produce a very nice mapping from example scenarios to the unit
test display. If you are using another CI server, this may be possible
as well by using the xsl to convert the jbehave reports to junit reports
and
After switching to AnnotatedPathRunner to get prettier test reports, I
noticed that this is done via the RunNotifier parameter, which is
currently only used in this notifier. Would it be possible to use the
same approach for a normal setup where no annotations, DI etc is used?
I am currently
, Pico and
Spring. There are examples for each one.
cheers
Cristiano
On 22/12/11 19:26, Alexander Lehmann wrote:
I have started using AnnotatedPathRunner to run stories as Junit in
eclipse, based on the TraderAnnotatedPathRunner example.
This works well for Step classes that do
Hi Graham,
using jbehave without maven or ant is possible, but it's a bit difficult to
set up if you do not want to use any of the common tools at all, since you
have to get the dependencies somehow.
Which tools are you able to use if you are not using ant or maven, e.g.
Eclipse, ivy, shell
I have started using AnnotatedPathRunner to run stories as Junit in
eclipse, based on the TraderAnnotatedPathRunner example.
This works well for Step classes that do not have parameters in the
constructor by listing the classes in the @UsingSteps annotation.
I have no idea, however, how this
29 matches
Mail list logo
