Getting caught up on email. ;-)
I didn't realize that profile existed. So you can start WF in debug mode (especially easy in Eclipse) and run tests against it. Sometimes I put tests in a WAR so I can do that, but wildfly-arquillian-container-remote would make life easier.
I think the wildfly-arquillian-container-remote one is there to allow testing against an already running container, without having arquillian control its lifecycle.I personally don't use that so often, but perhaps others have different opinions / habits?Cheers
On Fri, Dec 13, 2019 at 7:00 PM Rebecca Searls <email@example.com> wrote:
Module testsuite/arquillian-utils has profile arquillian.remote. This profile
uses archive org.wildfly.arquillian:wildfly-arquillian-container-remote when
running tests within the module. The default profile in arquillian-utils uses
archive org.wildfly.arquillian:wildfly-arquillian-container-managed. Both
profiles have existed since the creation of module testsuite/arquillian-utils
Is this still used? Who uses it? I am inclined to remove it if no one
vouches for its use.
resteasy-dev mailing list
_______________________________________________ resteasy-dev mailing list firstname.lastname@example.org https://lists.jboss.org/mailman/listinfo/resteasy-dev