-
1. Re: Next Steps for Arquillian
dan.j.allen Feb 8, 2010 12:15 AM (in response to alrubinger)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.j.allen Feb 10, 2010 7:39 PM (in response to alrubinger)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.
- 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.
-
3. Re: Next Steps for Arquillian
alrubinger Feb 10, 2010 8:09 PM (in response to alrubinger)Good stuff, Dan. I think this post is closely related to points we should cover at the meeting:
..just to link the Threads
S,
ALR