We are using Seam 2.0.1 GA on our project and have been very happy with the integration testing in Seam. We have 2500+ tests with 60% of them being integration tests. You are correct when you talk about the classpath being picky. From our experience, you need to have these 3 jars at the top of the classpath (in this order):
Also, at least with 2.0.1 GA, Seam wants to re-bootstrap the container with each test class. I believe this has been fixed in later releases, but we put in a fix for this in a subclass of SeamTest for this.
Lastly, as more and more Seam components were added we were randomly getting a ConcurrentModificationException in the container. You need to apply a patch from here to the container:
Thanks alot for your reply Cory, I will try your recommendations and let you know the outcome.
You could give JSFUnit a try as an alternative to embedded.