Hi Nodje,
comment is fine as I don't find time to write anything on my blog since
a long time.
Cheers,
Marc.
nodje wrote:
Hi Marc,
it works great! thanks a lot.
<systemPropertyVariables>
<wt.headless>true</wt.headless>
</systemPropertyVariables>
You should update your blog. Or do you want me to post a comment on it?
rgds
-nodje
Marc Guillemot wrote:
Hi Nodje,
did you try to pass wt.headless as system property? It seems that it has
to be done just like for the surefire-plugin:
http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
Cheers,
Marc.
--
Blog: http://mguillem.wordpress.com
nodje wrote:
Hi Siegfried,
pretty good deduction, I'm using 2) webtest-with-groovy-maven (as
described)
It seemed the better solution at the time.
-nodje
Siegfried Goeschl wrote:
Hi Nodje,
the point is that I do not know how you run your webtests
1) using the webtest-maven-plugin
2) webtest-with-groovy-maven (as described in the link)
3) using the maven-antrun plugin
When using the webtest-maven-plugin there is simply no
WebTestMonitor.groovy so that looks pretty much like 2) or 3)
Siegfried Goeschl
When lookinb
On 22.04.10 09:56, nodje wrote:
Hi Siegfried,
Mark's blog explains it all, this is based on this post that I have
figured
my CI server build:
http://mguillem.wordpress.com/2009/04/30/webtest-with-groovy-maven-and-eclipse/
I've tried your option -Djava.awt.headless=true but to no avail.
Here's an excerpt of the error on a Linux machine:
wt.webtestMonitor:
[echo]
/root/Documents/project/alpha2/target/test-classes/webtest-resources/tools/WebTestMonitor.groovy
Exception in thread "AWT-EventQueue-0"
org.codehaus.groovy.runtime.InvokerInvocationException:
java.lang.RuntimeException: Failed to create component for 'frame'
reason:
java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an
operation
which requires it.
cheers
Siegfried Goeschl wrote:
Hi nodje,
I have not noticed such a pop-up yet
+) is this a pop-up to monitor the test progress or test result?
Regarding test progress - this would be strange because this are
Groovy
scripts (not shipped and not called) and I'm sure I would not open a
browser to view the test results.
+) or is this the old AWT headless issue (-Djava.awt.headless=true)
Cheers,
Siegfried Goeschl
On 22.04.10 04:02, nodje wrote:
Thanks for letting know Michael.
Unfortunately I presume this is not an option for a Maven run build.
I can't find any reference to this option on the website.
cheers
Habbert, Michael (Key-Work) wrote:
Hi nodje,
property-file:
show.monitor=false
and
build.xml:
<condition property="wt.headless">
<equals arg1="${show.monitor}" arg2="false"
casesensitive="true"
trim="true" />
</condition>
Is working fine form e.
Cheers
Michael
-----Ursprüngliche Nachricht-----
Von: [email protected]
[mailto:[email protected]]
Im Auftrag von nodje
Gesendet: Mittwoch, 21. April 2010 06:42
An: [email protected]
Betreff: Re: [Webtest] Using 'mvn verify -Dwt.headless' doesn't skip
the
console
Hi,
sorry for the late reply. Adding -Dwt.headless=true doesn't make a
difference.
It still tries to popup the WebTest result interface on the CI
server.
cheers,
-nodje
Marc Guillemot wrote:
Hi,
try following:
-Dwt.headless=true
Cheers,
Marc.
--
Blog: http://mguillem.wordpress.com
nodje wrote:
Hi,
I'm trying to get rid of the console for CI testing.
-Dwt.headless is the only option I've found so far, but to no
avail
in
my
case.
Had anyone successfully ran headless in a verify phase?
cheers
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
