Nope, it does not have to be arquillian per-se. As long as there is some
way I can:
1) start the thing when the tests start
2) stop it after they are done
3) easily deploy the test bundle(s)
On Thu, Apr 23, 2015 at 3:49 AM, Hardy Ferentschik <hardy(a)hibernate.org>
wrote:
Hi,
does it have to be Arquillian? In Search and Validator we are using Pax
Exam[1]
for Karaf integration tests. See for example OsgiIntegrationTest [2] in
Validator.
It works quite well, but no matter whether Pax Exam or Arquillian it gets
painful
once you need to debug the tests. There it is often the best approach to
have a local
Karaf instance into which you deploy your features to verify that it
actually deploys.
From my conversations with Brett I concluded that the Arquillian approach
is more fragile than
Pax Exam, but I don't have actual experience with Arquillian + Karaf.
--Hardy
[1]
https://ops4j1.jira.com/wiki/display/paxexam/Pax+Exam
[2]
https://github.com/hferentschik/hibernate-validator/blob/HV-978/osgi/inte...
On Wed, Apr 22, 2015 at 04:11:10PM -0500, Steve Ebersole wrote:
> Anyone know of tutorials or guides on
> using arquillian-container-karaf-managed? Or willing to help me figure
out
> using that in hibernate-osgi tests?
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev