-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuxeo testing issues #114
Comments
Hi,
I've pushed a fix (commit fd3bda4). About the testing contributions which are currently located in easysoa-registry-core/src/main/resources/test/, they
See below the corresponding interfaces Javadoc. public @interface Deploy { public @interface LocalDeploy { I'm looking in the EasySOA wiki if there's some page dedicated to tests with Nuxeo tests framework for copying the above Regards, Le 27/04/12 12:22, Marwane Kalam-Alami a écrit :
Julien Carsique, DevOps, Nuxeo (Paris, France) |
Hi Julien, Thanks for your answer. In particular I didn't know we could provide a Manifest for the tests, it might explain a few things! Now I still have the dataSource errors, but I think it's only because you forgot to commit the |
Ouch! Sorry, that's pushed. Le 30/04/12 10:59, Marwane Kalam-Alami a écrit :
Julien Carsique, DevOps, Nuxeo (Paris, France) |
Awesome, it works fine now. Thanks again |
Please see the problems below to help up start with good practices for Nuxeo testing. Fixing
easysoa-registry-core
tests should be enough to let us fix the others.Note: The 'scaImport' test not passing is not part of these issues.
1. Datasource stacktrace in most tests
Stacktraces about sata-source configuration issues are logged all over the tests (but don't refrain them from passing).
2. General use of RunnerFeatures
We would like a review of our use of the Nuxeo testing framework, as we're not sure we're using it right (we often face various classpath/deployment problems). We mainly need some feedback on our way to implement reusable RunnerFeatures (see
easysoa-registry-core/...main.../org/easysoa/test/...
) and our use of @Deploy and @LocalDeploy annotations.The text was updated successfully, but these errors were encountered: