I don't have any knowledge of Cactus/MockObjects. I had never thought
about such a testing strategy. Thanks for the info.

Anto Paul


On Thu, 23 Sep 2004 09:34:34 -0400, Shapira, Yoav <[EMAIL PROTECTED]> wrote:
> 
> Hi,
> 
> >Do you run unit test using Cactus for all code changes ? Just to know
> >?. I feel that such tools are useful for those who is responsible for
> >integration testing.
> 
> It's not that simple (at least for me and the organizations I've worked
> for/with).  I don't have the luxury (and few people do) of leaving all
> "integration testing" to QA in the first place.  Even if I did, I
> wouldn't consider a test like making sure a servlet can work with a
> connection pool an integration test (and such a test would obviously
> require JNDI).  And even in places that consider that an integration
> test, I've found the quality of QA testing to be mediocre at best, and
> downright clumsy on average.
> 
> So I, and the developers I manage, end up writing a good amount of tests
> that aren't plain JUnit tests: we use Cactus, MockObjects, and a variety
> of other tools.  They get run automatically on a nightly basis on our
> test server, so we don't spend any time running them, we just check the
> results in the morning.  There's also a nightly Clover run to give us an
> idea of how we're doing in test code coverage.
> 
> I didn't stumble into this approach or invent it: there's an ample body
> of both theoretical SD research and practical experience that suggest
> waiting for QA to conduct all integration testing results in
> significantly worse product quality and delayed shipping.  Tools like
> Cactus are priceless to quality-oriented shops.
> 
> Yoav
> 
> 
> 
> 
> >
> >Anto Paul
> >
> >
> >On Thu, 23 Sep 2004 09:12:12 -0400, Shapira, Yoav
> <[EMAIL PROTECTED]>
> >wrote:
> >>
> >> Hi,
> >> OK.  To each their own testing philosophy ;)
> >>
> >> Yoav Shapira
> >> Millennium Research Informatics
> >>
> >>
> >>
> >>
> >> >-----Original Message-----
> >> >From: Anto Paul [mailto:[EMAIL PROTECTED]
> >> >Sent: Thursday, September 23, 2004 9:10 AM
> >> >To: Tomcat Users List
> >> >Subject: Re: [OT] Handling JDBC transactions
> >> >
> >> >Simulating real world is a QA fellows job. I write code, foresee any
> >> >bugs that it may have, write tests for it, run tests using Ant,
> deploy
> >> >to Tomcat(copy files) and test. Only JSP pages one need to test
> using
> >> >a container with every change for- for the visual layout.
> >> >
> >> >rgds
> >> >Anto Paul
> >> >
> >> >
> >> >On Thu, 23 Sep 2004 09:02:06 -0400, Shapira, Yoav
> >> <[EMAIL PROTECTED]>
> >> >wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> >Cactus is in-container testing(I assume). Takes time. I want to
> test
> >> >> code
> >> >> >as
> >> >> >I write it.  Already the development time for deploying an
> >> application
> >> >> is
> >> >> >high because of having a different source directory than web
> >> >> application
> >> >> >directory and of Ant.
> >> >>
> >> >> Good luck.  If you want to have tests that simulate real-world
> >> >> conditions, not just simple unit tests, you'll wake up to things
> like
> >> >> Cactus soon enough ;)  Or maybe create your own framework for
> testing
> >> >> code as you write it complete with the plumbing required.
> >> >>
> >> >> Yoav
> >> >>
> >> >> This e-mail, including any attachments, is a confidential business
> >> >communication, and may contain information that is confidential,
> >> >proprietary and/or privileged.  This e-mail is intended only for the
> >> >individual(s) to whom it is addressed, and may not be saved, copied,
> >> >printed, disclosed or used by anyone else.  If you are not the(an)
> >> intended
> >> >recipient, please immediately delete this e-mail from your computer
> >> system
> >> >and notify the sender.  Thank you.
> >> >>
> >> >>
> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> >> For additional commands, e-mail:
> [EMAIL PROTECTED]
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >> >--
> >> >To strive,to seek,to find and not to yield
> >> >
> >>
> >---------------------------------------------------------------------
> >> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> >For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >>
> >> This e-mail, including any attachments, is a confidential business
> >communication, and may contain information that is confidential,
> >proprietary and/or privileged.  This e-mail is intended only for the
> >individual(s) to whom it is addressed, and may not be saved, copied,
> >printed, disclosed or used by anyone else.  If you are not the(an)
> intended
> >recipient, please immediately delete this e-mail from your computer
> system
> >and notify the sender.  Thank you.
> >>
> >>
> >
> >
> >
> >--
> >To strive,to seek,to find and not to yield
> 
> 
> 
> 
> This e-mail, including any attachments, is a confidential business communication, 
> and may contain information that is confidential, proprietary and/or privileged.  
> This e-mail is intended only for the individual(s) to whom it is addressed, and may 
> not be saved, copied, printed, disclosed or used by anyone else.  If you are not 
> the(an) intended recipient, please immediately delete this e-mail from your computer 
> system and notify the sender.  Thank you.
> 
> 



-- 
To strive,to seek,to find and not to yield

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to