Much of the code between the JUnit task and the Quilt task does the same stuff. I am going to try to work with the JUnit Task maintainers for Ant, and refactor something so the Quilt task can get all the features of the JUnit task.
Currently Quilt is almost integrated into Maven. After this comes the next step, making the reports look nice. With the abilities of the Maven team, I hope to have some slick reports generated from Quilt.
It will not be long before I sit down and work out the APC coverage as documented by Thomas Ball in 1996. This will provide Acyclic Path, Branch and Statement coverage all in the same instrument package.
Its no mistake that Ant and Maven are the first integrations for Quilt. They are first because I use them. You (the reader) may use another IDE like JBuilder or IntelliJ. If you take the time to get Quilt integrated, I and many others will be happy that you did.
It should be easy to integrate Quilt into a Tomcat container. Thus you will be able to run coverage tests over servlets and JSPs.
Once the Tomcat integration is done, it should be easy to go into the EJB containers, and integrate Quilt with JBoss. Coverage information from embedded beans could be useful.
Any place where code runs, it should be easy to integrate Quilt. Containers I'm looking at in the future are Avalon and Cougaar (only because I work with Cougaar on a daily basis.)
Statement and Branch coverage are all fine and dandy for Unit tests, but Integration testing requires a different set of tools. Integration testing would measure intra- and inter- package calls between classes. These can be checked against all the different call patterns and such.