On Wed, Jul 28, 2010 at 9:47 AM, Brent Daniel <[email protected]> wrote: > POL_3002 can be ignored -- the test doesn't exist anymore. > > POL_4015 and POL_4016 shouldn't be run, either. They test that an > exception is thrown when a runtime doesn't support directly attached > (4015) or externally attached (4016) policy sets. Since we support > both, both tests will fail. OASIS has addressed this by providing > different versions of the JUnit test runner (AllTests, > AllExtAttachTests, and AllDirectAttachTests.) > > I'm surprised that you're both seeing 4033, 9022, and 9023 failing, > though. How are they failing? >
Ok I've committed excludes to the otest policy pom.xml surefire config to not run 3002, 4015 and 4016. 9022 and 9023 are failing for me as the intent names come out in a different order to what we have in the err msgs file, its different for me if i run from mvn or eclipse with asyncInvocation before propagatesTransaction in one and the other way round in the other. I've committed a change to the err msgs file to use *** for the intent name in the err msgs, though i accept that makes the test slightly less explicit so if anyone has a better approach ... That leaves just 4033 failing for me which is due to: Caused by: org.oasisopen.sca.ServiceRuntimeException: [Contribution: POL_4033, Artifact: META-INF/definitions.xml, Definitions: jar:file:/C:/Tuscany/svn/otests/new layout/tuscany-policy-test-runner/../sca-policy/POL_4033/target/POL_4033.zip!/META-INF/definitions.xml] - ContributionReadException occurred due to: org.apache.tus cany.sca.contribution.processor.ContributionReadException: javax.xml.xpath.XPathExpressionException and that only happens in mvn it works ok in eclipse. I'll try to debug it a bit further. ...ant
