Here are some specific areas that I think we should have more tests for: 1) Command line tools like deploy, client, jaxws-tools, etc. and their gshell counterparts.
2) Deploying applications using the different methods or options: using the command line tools, using the console, hot deploy, offline, in-place, etc. 3) Plugin infrastructure: export a plugin, assemble a server, etc. In general, I think it would be a good exercise to come up with a list of key features of Geronimo and make sure they are well covered by tests. Jarek On Tue, Feb 26, 2008 at 3:44 PM, Lin Sun <[EMAIL PROTECTED]> wrote: > Hi, > > I am interested in collecting ideas on how we can improve user > experience with the geronimo 2.x server, particularly, what type of > testing we can do for each geronimo major release to identify probs > and resolve them. > > I think it would be nice to have a set of test (either automated or > manually) other than tck that we run to verify various functions in > geronimo for each major release. Currently, we probably only run a > very small amount of testing other than tck, our automated testing > during the build and the few samples we have. > > One thought is to add more test samples. Seems to me people are > trying different things with geronimo server and most of the stuff > they tried are not covered by our samples. Any ideas what other > samples may be good to work with geronimo? > > The other thought is to grow test cases from our JIRA system or users. > Encourage folks to attach/contribute their test cases. > > Also, what g functions do folks think we need more testing? > > Thanks, Lin >
