[jbosstools-dev] Arquillian testing in JBoss Tools
Snjezana Peco
snjezana.peco at redhat.com
Wed May 18 12:35:46 EDT 2016
On 5/17/2016 11:09 PM, Brian Fitzpatrick wrote:
> So there really are no docs for this thing beyond what I have found at
> the github repo -https://github.com/jbosstools/jbosstools-arquillian
>
> I haven't quite figured out the relationship between an arquillian
> profile, a maven profile, and the run configuration...
>
Arquillian profiles are specific maven profiles enabling you to control
an arquillian container (server).
Try the following:
- make sure that Eclipse is started with JDK, not with JRE
- install JBoss WildFly
- import a Java EE Web Project
- right click the project and select Run As Arquillian JUnit test
- call Select Maven Profiles and select the arq-wildfly-managed profile
- wait for Eclipse to build the project
- set the JBOSS_HOME variable
- run tests
If you select some managed profile (arq-wildfly-managed, for instance),
Arquillian will start a server, run the tests and stop the server.
If you are using a remote profile (arq-wildfly-remote, for instance),
you have to start the server. Arquillian will find it and run the tests
on it.
I think this way is easier because everything should work with the
default settings.
You need to choose only one arquillian profile.
Based on your log, you seem to have invalid the arquillian.xml file. Try
to use the following arquillian.xml:
<?xml version="1.0" encoding="UTF-8"?>
<arquillian xmlns="http://jboss.org/schema/arquillian"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://jboss.org/schema/arquillian
http://jboss.org/schema/arquillian/arquillian_1_0.xsd">
<defaultProtocol type="Servlet 3.0" />
<container qualifier="jboss" default="true">
</container>
</arquillian>
Snjeza
> For instance, I have a project that has an existing Arquillian test.
>
> I was able to specify a maven profile - I specified default and
> arq-managed. Started the server inside Eclipse. Set a JBOSS_HOME
> environment variable pointing to it... Try to kick it off and get:
>
> org.jboss.arquillian.container.spi.ConfigurationException: jbossHome
> '${env.JBOSS_HOME}' must exist
> at
> org.jboss.arquillian.container.spi.client.deployment.Validate.configurationDirectoryExists(Validate.java:139)
> at
> org.jboss.as.arquillian.container.DistributionContainerConfiguration.validate(DistributionContainerConfiguration.java:103)
> at
> org.jboss.as.arquillian.container.managed.ManagedContainerConfiguration.validate(ManagedContainerConfiguration.java:65)
> at
> org.jboss.arquillian.container.impl.ContainerImpl.createDeployableConfiguration(ContainerImpl.java:115)
> at
> org.jboss.arquillian.container.impl.ContainerImpl.setup(ContainerImpl.java:181)
>
> What am I doing wrong? Something simple I'm guessing...
>
>
> On Tue, May 17, 2016 at 2:07 PM, Max Rydahl Andersen
> <manderse at redhat.com <mailto:manderse at redhat.com>> wrote:
>
> On 17 May 2016, at 19:07, Brian Fitzpatrick wrote:
>
> Honestly I'm not sure. We have a case where users can really
> only test
> Camel routes running on a Fuse-on-EAP instance through Arquillian.
>
> We either have to run it at a command line via maven - mvn
> clean test
> -Parq-managed - or find a way to do it in the tooling.That is
> what I was
> hoping the Arquillian tooling would allow us to do. I wasn't
> able to get it
> running on Friday with the Arq tools installed, but I still
> want to work on
> it to see whether it's a workable solution. I suspect the
> tools may at the
> very least help create Arquillian-tests, but I don't know yet.
>
>
> the arqullian tools mainly enables being able to run arquillian
> tests via
> eclipse junit test runners without having to wait for maven.
> (simplified description ;)
>
> I really need to go through the docs to see what it can do.
>
> Ultimately we'd like to be able to do all Fuse tasks in the
> tooling... i.e.
> Create a project. Test and debug a project. Deploy a project.
>
> We can do that in a Fuse server set-up, but not with Fuse on
> EAP right now.
>
>
> is this not because with "pure" fuse server you relay everything
> through maven
> and actually the tools don't do much ?
>
>
>
> Let me clarify... **I'm** not able to do that right now - I'm
> not saying
> it's not possible. :) So the problem may purely exist between
> the chair and
> the keyboard at the moment. :)
>
>
> --Fitz
>
>
> On Tue, May 17, 2016 at 8:09 AM, Max Rydahl Andersen
> <manderse at redhat.com <mailto:manderse at redhat.com>>
> wrote:
>
> On 13 May 2016, at 19:51, Brian Fitzpatrick wrote:
>
> Thanks Fred.
>
>
>
> is this something integration stack would like to see
> added or just for
> your personal
> benefits ?
>
> For now its been low-priority since we have not had many
> requests for it
> and noone to maintain the plugin actively.
>
> /max
>
>
> On Fri, May 13, 2016 at 11:51 AM, Fred Bricon
> <fbricon at redhat.com <mailto:fbricon at redhat.com>> wrote:
>
> In JBDS, Arquillian tools are available in Red Hat
> Central, software tab,
>
> with Early Access enabled
>
> On Fri, May 13, 2016 at 1:46 PM, Brian Fitzpatrick
> <bfitzpat at redhat.com <mailto:bfitzpat at redhat.com>>
> wrote:
>
> Awesome. Thanks Fred - that may get me what I'm
> looking for.
>
>
> I take it that those bits are JBT only and not
> JBDS at this point?
>
> On Fri, May 13, 2016 at 10:57 AM, Fred Bricon
> <fbricon at redhat.com <mailto:fbricon at redhat.com>>
> wrote:
>
> See
> http://tools.jboss.org/features/arquillian.html
>
>
> On Fri, May 13, 2016 at 12:55 PM,
> Jean-Francois Maury <
> jmaury at redhat.com <mailto:jmaury at redhat.com>
>
> wrote:
>
>
> What would you like to see ? Prepare the
> deployement ?
>
>
> Jeff
>
> On Fri, May 13, 2016 at 6:33 PM, Brian
> Fitzpatrick <
> bfitzpat at redhat.com
> <mailto:bfitzpat at redhat.com>
>
> wrote:
>
>
> Hi all,
>
>
> I'm going fishing for information
> here, but do we have any facility
> in
> JBoss Tools for helping folks
> create Arquillian tests?
>
> Seems that it would be a good fit
> for working with the
> Servers/Runtime
> framework maybe?
>
> --Fitz
>
> --
> Brian "Fitz" Fitzpatrick
> Sr. Software Developer, Fuse
> Eclipse Tooling
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> <mailto:jbosstools-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> <mailto:jbosstools-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
>
>
> --
> Brian "Fitz" Fitzpatrick
> Sr. Software Developer, Fuse Eclipse Tooling
>
>
>
>
>
> --
> Brian "Fitz" Fitzpatrick
> Sr. Software Developer, Fuse Eclipse Tooling
>
>
>
> _______________________________________________
>
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> <mailto:jbosstools-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> /max
> http://about.me/maxandersen
>
>
>
>
> --
> Brian "Fitz" Fitzpatrick
> Sr. Software Developer, Fuse Eclipse Tooling
>
>
>
>
>
> /max
> http://about.me/maxandersen
>
>
>
>
> --
> Brian "Fitz" Fitzpatrick
> Sr. Software Developer, Fuse Eclipse Tooling
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160518/ed73908b/attachment-0001.html
More information about the jbosstools-dev
mailing list