I think users will find samples on how to test controls very valuable. However, as Ken pointed out, most control tests require a container. This makes testing controls a nontrivial task. Currently, you have to write a JPF to test a control in a container, which entails deploying a webapp. Unit tests are usually done using HTTPUnit. Perhaps we can work on a control test template separate from the control template. This will provide control developers a guide to test controls without complicating the control template which is meant to simplify control development. Control developers can choose to use the test template to develop test cases for their controls as they like.
-----Original Message----- From: Ken Tam Sent: Wednesday, October 27, 2004 10:09 PM To: Beehive Developers Subject: RE: Blank controls app template checked in I thought about that, but ultimately decided against it. It seemed to me that the 2 main purposes of the sample template are: 1) make it easy for users to start building controls 2) showcase the aspects of the build that are specific to controls Ie, I thought for the purposes of #2, the build.xml should be as minimalist as possible. I can see how it might be interesting for app developers (users) to add unit tests into the build for their controls (although it's worth keeping in mind the fact that most interesting controls tests will require a container), however I guess I feel it's appropriate to let those app devs make that decision on their own. Anyone else have an opinion here? > -----Original Message----- > From: Dan Diephouse [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 27, 2004 4:58 PM > To: Beehive Developers > Subject: Re: Blank controls app template checked in > > Ken, > Just a thought, it would be good to integrate tests into the > build as well. Maybe a src/main and a src/test directory > with the build running the junit tests? A sample test would > be cool too... > > - Dan > > Ken Tam wrote: > > >I just checked in a "blank" template for controls development into > >/samples/controls-blank (it lives in the same place in the distro). > >The idea is that users can clone this template and it has a > build.xml & > >dir structure that will compile controls and archive them into a > >control jar. > > > > > > > >Steve, it would be great if your tutorials/docs reference this - it > >should save you time as well. It's pretty straight forward > - there's a > >build and a clean target, and they do what you'd expect :-). > > > > > > > >Let me know if there are any questions. > > > > > > > > > > -- > Dan Diephouse > Envoi Solutions LLC > http://envoisolutions.com/people/dan > >
