anonymous wrote : | Adrian Brock's 1st Law of Programming. | It it ain't tested it doesn't work. | | 1st Law Corollary | It it ain't tested the feature doesn't exist. ;-) | Sure, these are the laws I also work according to. anonymous wrote : | Why aren't there regression tests for these features in reactor/framework? | JBoss OSGi supports multiple OSGi frameworks, for the reason that standard OSGi is already usable in AS. What we do with the OSGi example and functional test is a specific solution to the general problem of Maven integration testing http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing Anyhow, the MC framework needs to work in AS and the OSGi examples must run in AS. This is not something you can do in an Eclipse unit test. I realize, that the building the installer, installing the framework, starting the target container, running the examples against the target container is not a practical prerequisite for an SVN commit. However, everybody should at least be aware of the functionality that already works and is being tested. One click on the public hudson instance can pickup potential integration issues, which can then be looked at and fixed locally. It'd be good if you could trigger the integration tests as part of your normal commit routine. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266714#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...