JSFUnit 1.3.0 is out. There are only three interesting changes:
- A new API call on RichFacesClient for Drag and Drop
- Updates for compatibility with HtmlUnit 2.8
- One JSFUnit bug fix
But the big story is the one tiny JSFUnit bug fix submitted by Aslak Knudsen. You see, that fix enables JSFUnit to integrate with Arquillian. If you are not familiar with Arquillian, this is a new JBoss project that handles deployment and test execution for in-container tests. It's an elegant, modern replacement for what we do now with Cactus and Cargo.
So going forward, you will be able to run your JSFUnit tests using either Arquillian or Cactus/Cargo. The advantages you will have with Arquillian are:
- Full JUnit 4 support (yay! we can finally use the @Test annotation!)
- TestNG 5 support (yay! if you prefer TestNG)
- Resource injection into your test classes (stuff like @Inject or @EJB can go right into your test)
- Testing for subsets of your WAR. For instance, if I only want to test two facelets and one managed bean it will package those into a small WAR, deploy it, and run the test. This is great for development because single tests will run much faster without creating the whole giant WAR.
So when can you try out the JSFUnit/Arquillian combo? Aslak already has a proof of concept. It looks like we may be ready to let it loose in just a few days. Stay tuned.
So long, and thanks for all the fish,
P.S. Note that some dependency versions have changed. Check out the getting started page for the complete list of jars you need to upgrade.