Eric, I'm sure you'll love the book we're writing :-)
Here is the table of content (not finalized but it should give you a pretty good idea of its content): Part 1 - JUnit distilled Part 1 introduces the JUnit platform through a series of simple, hands-on examples. How to unit test Java applications is explained by creating tests for Java applications. 1 - Introducing JUnit Chapter 1 walks through creating a test for a simple object. We introduce the benefits, philosophy, and technology of unit testing along the way. As the tests grow more sophisticated, we present JUnit as the solution for creating better tests. 2 - Exploring JUnit Chapter 2 delves deeper into the JUnit classes, lifecycle, and architecture. We take a closer look at the core classes and the overall JUnit lifecycle. To put everything into context, we also look at several example tests, like those you would write for your own classes. 3 - Sampling JUnit Chapter 3 presents a sophisticated test case to show how JUnit works with larger components. The subject of our case study is a component found in many applications: a controller. We introduce the case-study code, identify what code to test, and then show how to test it. Once we know that the code works as expected, we create tests for exceptional conditions, to be sure our code behaves well even when things go wrong. 4 - Examining Junit Chapter 4 looks at the various types of unit tests, the role they play in the an application's lifecycle, how to design for testability, and how to practice test-first development. 5 - Automating JUnit Chapter 5 explores the various ways you can integrate JUnit into your development environment. We look at running JUnit from the command line or an applet, as well as from Ant, Maven, and Eclipse. Part 2 - Testing Strategies Part 2 investigates strategies for testing the types of complex objects we find in professional applications. 6 - Coarse-grained testing with Stubs 7 - Testing in isolation with Mock Objects 8 - In-container testing Stubs, Mocks, or Cactus: Which to use when Part 3 - Junit Frameworks Very short description (and examples) of the framework we will look at in more details in Part 4. 9 - HttpUnit 10 - Cactus 11 - dbUnit: Database testing 12 - MockObjects.com (Note, includes EasyMock and co) 13 - Struts Test Case: Testing Struts Actions Part 4 - Testing Components Shows how to unit test different kinds of components using the different strategies explained in Part 2. Demonstrates pros and cons of each and how to marry them. 14 - Testing Servlets and Filters 15 - Testing Server Pages and JSP Taglibs 16 - Testing Database Applications 17 - Testing EJBs Appendix Hope you like it :-) -Vincent > -----Original Message----- > From: Chiu, Eric T [mailto:[EMAIL PROTECTED]] > Sent: 05 February 2003 17:24 > To: 'Cactus Users List' > Subject: RE: best practices on writing Cactus tests? > > Yes, this is a start, but the Junit docs are more about > how to write unit tests in general... > http://junit.sourceforge.net/doc/cookstour/cookstour.htm > > And don't address issues specific to Servlets, EJBs, > JSP, or the J2EE container. > > If you have a brain tumor, do you go to a family care > physician? > > -----Original Message----- > From: Mark Wehby [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 05, 2003 10:26 AM > To: Cactus Users List > Subject: Re: best practices on writing Cactus tests? > > > I would suggest looking at www.junit.org for guidelines. > > Mark Wehby > > > ----- Original Message ----- > From: "Chiu, Eric T" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, February 05, 2003 10:14 AM > Subject: best practices on writing Cactus tests? > > > > Has anyone written up a guideline on > > best practices for writing Cactus tests? > > > > It is an interesting topic, perhaps Vincent > > is putting it in his book? > > > > Thanks, > > Eric Chiu > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
