The following test classes are failing for reasons that seem related to either the new AS7 env or Java7 runtime, or both. SynchronizationManagerBeanTest The XML seems to be ignoring placement of the namespaces in the root element. The tests will currently dump the XML, so run the test to see the XML. JndiAccessTest This is due to changes in JNDI in AS7. Local methods are accessible to the scripts. Neither of these should be worked on until the rhq-on-as7 branch is more mature and other integration test issues are resolved.
added lzoubek to the notify list for this BZ
oh shoot ... this is AS7 container ... not AS7 plugin.
question: how might this failure manifest ... from an end-user perspective. if we know this, QE can keep an eye out ... and it will be useful to know for verification purposes.
SynchronizationManagerBeanTest failure manifests in inability to import any exported server configuration (using SynchronizationManager in the CLI). The JndiAccessTest failure is a security issue allowing the server-side scripts (i.e. alert scripts) access to our local (aka non-public) API as well as database connection etc, essentially circumventing the authorization level granted to them by the associated user that the scripts run as.
Also failing are the PERF tests. Heiko and/or Lukas will need to help with these. The DB setup stuff seems to be having issues.
The JndiAccessTest(s) and the SynchronizationManagerBeanTest (and the actual SynchronizationManagerBean) have been fixed to work under AS7. Perf tests are still commented out ATM.
The ldap test class is passing and activated. Only the Perf test classes have yet to be run. I'll need to ask around to see what state these tests were in even prior to the env changes.
RHQ has been fully ported to AS7 and the testsuite is passing. Closing this bug as obsolete.