Good question. I'd say this probably falls in the case where we should create a tests module, but since we have no way of actually running tests against a live forge distribution, it's going to be difficult to automate this. I would say that our first task should be to enable testing against an actual distribution by creating an Arquillian container and SPIs in Forge to enable remote control (probably like what you have done with JBoss Tools.) Not to put too much on your plate, but can I add this to your list of medium-term objectives? Perhaps not for the next 2 weeks, but I'm guessing that it will be very similar to booting forge from JBoss Tools as well. Actually, yes, the more I think about it - you could probably re-use almost everything (another why you should really push what you've done for JBoss Tools into a Forge tooling API!) If I got the module set up in the build, would that help you get started? What do you think? ~Lincoln On Wed, Mar 14, 2012 at 5:20 PM, Koen Aers <koen.aers(a)gmail.com&gt; wrote: Hi guys, In a discussion earlier today it was suggested that we should not only test the scaffolding with Forge generated entities but also with: 1) quick starts and the maven archetypes 2) the output of the database reverse engineering as generated by the Hibernate Tools plugin I will create a JIRA to track this issue but I first wanted to know where this issue (and these tests) should live? Cheers, Koen _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple" _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev