Issue 62 in soashable: Investigage JSUnit headless for CI server

[codesite...@google.com]

Issue 62: Investigage JSUnit headless for CI server
http://code.google.com/p/soashable/issues/detail?id=62

New issue report by h.iverson:
My thinking sofar is that we can use the selenium:xvfb task and wire that
display into the JSUnit launcher.

http://fisheye.codehaus.org/browse/mojo/tags/selenium-maven-plugin-1.0-beta-3/src/main/groovy/org/codehaus/mojo/selenium/XvfbMojo.groovy?r=6930#l109

It detects a usable display and writes to target/selenium/display.properties

Have not investigated JSUnit as a consumer yet.

Have not investigated using a profile activated by non-windows, non-osx yet.

Issue attributes:
Status: Accepted
Owner: h.iverson
Labels: Type-Task Priority-High

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Issue 62: Investigage JSUnit headless for CI server
http://code.google.com/p/soashable/issues/detail?id=62

Comment #1 by h.iverson:
Dug deep into the source code and determined that JSUnit 2.2 is
required for this to
work. It would be done by way of a custom ProcessStarter that specifies
DISPLAY. It
could be done with JSUnit 2.1, but there appear to be no plans of ever
releasing a
new version and we can't distribute code against a patched product.

I've opened an issue with the javascript-maven-tools plugin for the
task. I might end
up doing it.

http://jira.codehaus.org/browse/MOJO-1126