tests we run in the build: some currently commented out; could we enable them?

Here’s what we have now:

clients/java/pom.xml:63:                        **/ClientUnitTestSuite.java

clients/java/target/selenium-server/META-INF/maven/org.openqa.selenium.server/selenium-server-coreless/pom.xml:66:                        **/UnitTestSuite.java

server-coreless/pom.xml:66:                        **/UnitTestSuite.java

Other test suites are referred to but commented out:

clients/java/target/selenium-server/META-INF/maven/org.openqa.selenium.server/selenium-server-coreless/pom.xml:67:                        commented out: **/ServerTestSuite.java-->

clients/java/pom.xml:65:                        commented out: **/ClientDriverSuite.java

clients/java/pom.xml:66:                        commented out: **/ClientDriverPISuite.java

server-coreless/pom.xml:67:                        commented out: **/ServerTestSuite.java

In none of these latter cases is it explained why the suite is commented out.  Let’s make it a convention to note in the comment what our motivation is (e.g., “this test is unreliable on Mac and Linux”).

I’d like to enable every test that is reliable, and for the others, either fix them or file bugs to note that they are broken and represent work that should be done.  At that point, the comments in the code would be updated to refer to these JIRA bugs.  Sound reasonable?

On my system:

1.       ServerTestSuite works

2.       ClientDriverSuite is broken (due to across-the-board failures in the RealDealIntegration test)

3.       ClientDriverPISuite is broken (due to TestType failing)

Does anyone know of other problems (e.g., failures which only show on other platforms)?

And before I change anything in the pom’s, I need to get on the list of individuals who are alerted when the build fails.  Can someone please educate me as to how I can accomplish this?

Thank you!

n