snip... > > > > > > In the case binding-sca-calculator, for example, the ant build.xml runs > the > > sample using either the JSE or OSGI laucher. I've made no changes to > > launchers yet subject to discussion on the other thread. So in this case > the > > sample is just a contribution. There is a JUnit test but again this just > > calls the lanucher and treats the sample as a contribution. There is a > > client conponent in the sample that drives it. > > > > Ok > > > I'm looking at extending the distro module to run the ant script to > autmate > > the process we have struggled with in the past. In a way I'd rather have > > this happen as JUnit time but maybe that won't work out. I certainly need > > some help with the webapp version as we need to fire up cargo or > something > > to ensure that we can test the webapp deploy stage. > > > > If we are trying to solve the issue where we never run our samples > using ant/distribution, this is a good idea. How about something like > a "build smoke test" profile that, after building a distribution would > try to unpack and exercise it using ant ? > > > Sounds like a good idea to me.
There are a few things I think we can do to reduce the amount of time we spend testing releases, for example, - remove the need to generate ant scrips - allow the ant scripts to be run from mvn/eclipse at development time so people can try/develop them without explicitly deploying a distribution - have mvn automatically test the samples that require a webapp to be deployed to a webapp container (cargo?) - consider have the sample junit tests (or equivalent) run through the ant scripts. how to capture failures? - final smoke test (from luciano's comment above). Whatever we do earlier in the stream we need to test the samples as they appear in the distribution what else? Simon
