I was thinkking on a similar line, but thought of the following: Use custom Javadoc tags for each method, indicating testability, parameters, expected results, messages etc. We then have a custom Javadoc doclet. When we want a TestCase we run Javadoc with the custom doclet over the code and create the test cases automatically.
This can be made part of the build. The test parameters etc. are tied directly to the code, so it's pretty obvious what's going on. Brian --- Dharnidhar Vemuri <[EMAIL PROTECTED]> wrote: > Hi, > I was writing test cases for my project here and suddenly I got an > idea. The programmer is responsible for creating a TestCase class and writing > the assertions > etc. The functionality is being tested for a class finally. Why can't there > be a GUI that can write the extends TestCase... file for us. That GUI can > have a button that will > run the test cases for that class(es). > The GUI will display all the methods that are there in a class. It > has associated check boxes for each method. For each method there might be > many test cases > There might be a button that will allow us to enter all possible scenarios. > All the conditions are entered like wise for all the methods in the class (to > begin with) > Once all the inputs are given, it will ask for the filename and generate the > TestCase class. This looks simple. > Please feel free to comment on this. The same might be extended to > Server side test cases too. > > > Regards, > Dharnidhar > > ===== Brian Agnew http://www.oopsconsultancy.com OOPS Consultancy Ltd [EMAIL PROTECTED] +44 (0)7720 397526 ____________________________________________________________ Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
