IMO:
 
* Yes, we have thought about automatically generating test case classes. As Nicholas said, there is a task on the todo list to address this and I would be glad if someone could help. My idea was first to get a testing engine that worked and then later add some tools to help write test case, generate them, integrate better cactus with some IDEs, ...
 
* Yes, we have thought about writing custom javadoc tags for generating cactus test (in the same case as the EJBDoclet, now supersed by the XDoclet works - we could actually maybe even use the XDoclet). There is a task for that in the todo list too.
 
However :
 
* I don't believe we could never (or at least anytime soon - it might be possible in 25 years when we have intelligent AI ... :) ) automate the full generation of test cases. We can generate _skeletons_ but not the assertions for example. Why ? Because the JUnit tests are written in Java and if you want to put that in javadoc tags you would have either to invent a languager as rich as java or simply put jaba there ... which is bad because they are comment and you don't get the syntax verification, auto-completion, compiler checking, ... that you get with standard java classes ...
 
* So, I am not against generating skeletons. However, Javadoc tags for generating the skeletons might be overkill ? and may not be needed ?
* I would prefer to work for a tool that integrates with IDE and that can help write the skeletons for us. A bit like the javadoc checker in Netbeans for those who know it.
 
My opinion ....
Thanks for this interesting thread.
-Vincent

Reply via email to