Thanks a lot, I think your email was very helpful for me, I will be even more specific:
1) Using Ant, and running 10 tests in one build.xml, how can I complete all of them, even if the third one (for example) fails. Right now, since I don't catch the exceptions the build fails and the following tests are not run. 2) I am thinking about this functional test: I click on a link and then I submit a form, then I go and click on a second link and check if the result of that form submission is in the state and is correct. I would like to do this in one single test as the two requests (first and second link) are related. What is the best way to do it and extend the concept to multiple requests in series? Thanks a lot, Marco <>-----Original Message----- <>From: Vincent Massol [mailto:vmassol@;octo.com] <>Sent: Thursday, October 24, 2002 8:51 AM <>To: 'Cactus Users List' <>Subject: RE: About Cactus and Quality Assurance <> <> <> <> <>> -----Original Message----- <>> From: Marco Barcella [mailto:barcella@;appiancorp.com] <>> Sent: 24 October 2002 01:36 <>> To: Cactus Users List <>> Subject: About Cactus and Quality Assurance <>> <>> Hi, <>> I would really like to ask the following two things: <>> 1) I am using cactus for unit testing. When should the testing start <>in <>> the process of developing some code (beginning, end), in order to have <>the <>> best Quality Assurance in the shortest time? And also how to integrate <>> the testing with the development? Any ideas or links would be greatly <>> appreciated. <> <>The best is to do test-first development. Write your unit test first <>(before the code they test). Run the test: they will fail. Write the <>code. One by one the tests will turn from red to green. <> <>Why is it good? <>- because you get better tests (retrofitting tests to match code is <>always a best effort) <>- because you can then skip the detailed design phase as it is done in <>the unit tests. The unit tests also acts as design documentation. <>- because you will find that, as a result your code under tests is <>better written <> <>> 2) Considering to extend Cactus for functional testing, what, other <>than <>> HttpUnit, <>> could/should I integrate? What are the fundamental limits I will <>> encounter? <>> Thanks a lot, <>> Marco <> <>Cool! HttpUnit is already integrated but for checking results only. Do <>you mean you would like to extend Cactus to use it for sending requests, <>too (as part of a Web conversation)? <> <>It is definitely possible and I would be happy to help you and offer <>support for that. <> <>I don't see any fundamental issue (especially as I am happy to let you <>modify Cactus internals to make it more pluggable!). <> <>Before choosing the tools to use for that you need to tell us what you <>have in mind for functional testing. What would be a typical scenario? <> <>Thanks <>-Vincent <> <>> <>> <>> <>> -- <>> To unsubscribe, e-mail: <mailto:cactus-user- <>> [EMAIL PROTECTED]> <>> For additional commands, e-mail: <mailto:cactus-user- <>> [EMAIL PROTECTED]> <> <> <> <>-- <>To unsubscribe, e-mail: <mailto:cactus-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:cactus-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:cactus-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:cactus-user-help@;jakarta.apache.org>
