3 Replies Latest reply on Feb 10, 2010 8:09 PM by Andrew Rubinger

    Next Steps for Arquillian

    Andrew Rubinger Master

      So I've spent a couple hours this afternoon looking at source for the first time, and here's some impressions:

       

      • This is absolutely going to be a successful project.  Abstracting the harness of an integration test from the logic is a huge leap forward for users of all JEE containers.  It promotes choice and reduces time spent getting a working test environment.
      • The current state of the project is a fine proof-of-concept and prototype.  Props to Aslak for almost single-handedly taking it this far.

       

      That said, I think we now have a great opportunity to take care of the less-popular coding issues while we still have a small codebase.

       

      The first step I've taken is to ignore tests and get to a working build:

       

      http://jboss.hudson.alrubinger.com/job/Arquillian/4/testReport/

       

      Next I think we need to put some efforts into:

       

      • Documenting every feature on the Wiki as it's made
      • JavaDoc'ing everything.  With particular attention to detail in the API and SPI (ie. DeployableContainer) modules.
      • Adding unit test coverage

       

      An issue of particular immediate interest to me is: Choosing your Container.  This will enable us to have tests running in "demo" and "demo-testng" for all target containers (currently you must choose one as part of the build profile, and it doesn't work in the IDE without manually creating a run configuration).

       

      Features I do think we should keep in the short term is:

      • Container for GlassFish (Aslak)
      • Container for Jetty (me)
      • Container for OpenEJB (me)

       

      Aside from that, I'd love to see us work down our technical debt and narrow in on refining the core cases we have (including user docs).  Then we can grow.

       

      WDYT?

       

      S,

      ALR

        • 1. Re: Next Steps for Arquillian
          Dan Allen Master

          Andrew, fantastic summary. I'm really glad that you spent time to lay out a roadmap, review the design and lay down some practices.

           

          I plan on giving you some responses, but I first wanted to lay down the foundation of the reference guide so that we are also able to use it as well to help steer the project.

          • 2. Re: Next Steps for Arquillian
            Dan Allen Master

            ALRubinger wrote:

             

            So I've spent a couple hours this afternoon looking at source for the first time, and here's some impressions:

             

            • This is absolutely going to be a successful project.  Abstracting the harness of an integration test from the logic is a huge leap forward for users of all JEE containers.  It promotes choice and reduces time spent getting a working test environment.
            • The current state of the project is a fine proof-of-concept and prototype.  Props to Aslak for almost single-handedly taking it this far.

            +1

             

            We should also give credit to Pete for seeding a lot of the ideas behind Arquillian in the jboss-test-harness that currently powers the CDI TCK. So thanks Aslak and Pete!

            I'd love to see us work down our technical debt and narrow in on refining the core cases we have (including user docs).  Then we can grow.

            Good plan.

            • 3. Re: Next Steps for Arquillian
              Andrew Rubinger Master

              Good stuff, Dan.  I think this post is closely related to points we should cover at the meeting:

               

              Arquillian Design Kickoff

               

              ..just to link the Threads

               

              S,

              ALR