[GitHub] [netbeans] timboudreau commented on a change in pull request #1483: [NETBEANS-3076] Try to create unit-test with Gradle Projects

[GitBox <gi...@apache.org>]

timboudreau commented on a change in pull request #1483: [NETBEANS-3076] Try to create unit-test with Gradle Projects
URL: https://github.com/apache/netbeans/pull/1483#discussion_r324369637
 
 

 ##########
 File path: groovy/gradle.java/nbproject/project.properties
 ##########
 @@ -20,7 +20,10 @@ javac.source=1.8
 javac.compilerargs=-Xlint -Xlint:-serial
 nbm.module.author=Laszlo Kishalmi
 
+test-unit-sys-prop.test.netbeans.dest.dir=${netbeans.dest.dir}
+test-unit-sys-prop.java.awt.headless=true
 
 Review comment:
   @matthiasblaesing - if you can run a test headless, you should.  In particular, I know there are tests in exception handling code and the dialogs api for whether the toolkit is headless.  While there are tests that must open a UI a drive it, this tends to hijack focus on developer machines unless you run tests in a virtual X framebuffer.  Since thrown exceptions can result in dialogs unexpectedly popping up, any test that *can* run headless should prefer that, and only tests that simply must interact with windows and will fail otherwise should not be run headless.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists