Great advice so far, and thank you for the link to the article. The idea of testing the testing framework is very interesting! I guess it would be really straight forward to write a basic test that jumps into the framework, and just does a very basic probe making sure no exception gets thrown.
This would also avoid the problem of a method in a class getting 'stale'. For example if I write a class today and the test that uses it is removed from rotation (for whatever reason). The 'tester' script would inform me when it breaks (as opposed to a tester writing a script only to find the desired class broken). Thanks again, and I welcome any more ideas people have. I've been reading every article I can get my hands on and it seems to be helping me avoid the standard pitfalls (I hope). --------------------------------------------------------------------- Posted via Jive Forums http://forums.openqa.org/thread.jspa?threadID=4936&messageID=13768#13768 _______________________________________________ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
