Already 34 persons read this post... please... just a comment like: yes you can, no you never can, you can, but have to wait until the Czech-Developers do the next release ;-)
could anybody please give it a try?
A solution could be that I only use Graphene for functional tests and the peristence and business components are already deployed in the container, right?
Thanks in advance
from a linked issue it seems it should be possible implement this using mixed mode:
You have two options here:
- use Arquillian Persistence Extension (APE) extension to setup/tear-down the database
- handle the above manually
It also seems like the linked sample  doesn't actually use Arquillian Persistence Extension.
When using APE, the crucial thing here is that:
- Arquillian manages the deployment (you use @Deployment which has (testable=true)
- you use @InSequence and you setup the database in first step and reset it on the end
- you use Graphene in @RunAsClient test method
It would be interesting to connect those two, however generally I would not recommend to use Graphene for testing database layer.
You can use in-container testing to do so (testing on a level of JPA, CDI, EJB).
Even though, it would be interesting to use Graphene for full-scale testing, where APE roll changes to the database back.
Hi Lukáš, thanks a lot for your help!