Hi Stephen,
Oh yes - some of us are actively working in this area, including myself - this is exactly how we're using ZAP in Mozilla.
Theres some info on the wiki:
http://code.google.com/p/zaproxy/wiki/SecRegTests but its not as up to date as it should be ;)
Basically you can:
- Start ZAP in daemon mode (no UI)
- Proxy any functional tests you have through it
- Run the spider using the REST API to cover things your tests dont cover
- Run the active scanner
- Retrieve any alerts, and then fail the build (if relevant)
You can access the REST API either directly or via the Java or Python clients.
And if you'd like a client in another language and can help with it then we can work on that.
Theres still lots to do in this are (especially documentation;) but its a high priority for us (especially me).
As this is a bit bleeding edge we tend to discuss it in the
developer group, but happy to discuss it here as well.
Hows that sound?
Cheers,
Simon