Bob Tarling wrote: > Immediate thoughts are - > > Not enough of junit tests. > > Not enough physical separation of the application into modules. > > A small team so not enough manual testing. > > Old problems with poor threading now catching up on us. > > Lack of resource. > > Lack of specific required skills. > > Bob.
I assume that your own name wasn't intended to be part of this list of problems! Writing JUnit tests does not come naturally to most people, and it does require some encouragement and often some training. For anyone who has not done so already, I encourage them to read: http://junit.sourceforge.net/doc/testinfected/testing.htm Unfortunately, I am just as guilty, as I have not written any JUnit tests for ArgoUML. I often think that the JUnit tests that I might dream up would be too trivial to make a difference, and I imagine it would be difficult to write a JUnit test to handle GUI aspects. Also, implementing a few feature is far more rewarding that writing a test for an existing feature. Perhaps someone could give a worked example explaining which tests are are most useful for a given file, and where and how the tests are written, maybe in the wiki? Regards, Dave ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1357446 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
