[Jboss-dev-forums] [Design of Mail Services] - Re: Hibernate Mail Lists (and testing)

[<aco...@jb...>]

I'm not yet satisfied with our testing effort or comprehensiveness.  Its too painful ATM so something needs to change...

So I see different types of testing and we need to fill out to handle them as automatically as possible: 

1. Unit testing -- does a particular tiny component or class work.  Should be as independent of the appserver/etc as possible.

2. Component testing -- does a service work -- that probably should run in the server.

3. protocol testing -- run in the server but pass in scripts.  We have stuff for this but I don't know that we've really completed the toolkit.  

4. performance testing/functional testing - actually sending emails and making sure they are properly routed and how many can be routed per second/minute/hour.  This is the most difficult to automate.

Do I want to start the appserver to test some minor class or feature?  Probably not.  I'm probably willing to start a subset (which is what the present stuff does) to satisfy dependencies.  So do what you think is best but make sure I can just type "ant test" and that they don't take 5 years to run but I may need multiple targets depending on what i'm trying to accomplish.  We probably need to change our dir structure a bit for this.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884435#3884435

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884435