Tony Plate <[EMAIL PROTECTED]> writes: > How would a "unit testing" framework look different? (other than > maybe the ability to pick and choose tests easily and run them > quickly).
That is precisely it -- i.e. it's all testing, but it depends on where and how the tests are intended. (and then, how easy it is to write tests and run them..). The basic principle for unit tests is that you can associate a test with a particular unit of code, and relate the ability to run it to the function. So, one approach is to use the tests directory, with a file for each function with tests, and then have a means to test. This is reasonably easy to do. The other issue is the ability to group tests by dependencies (again, more of a UI functionality than a real problem). So, I think the point I'm trying to hammer at is the interface, not whether a framework which can be adopted is already in place. best, -tony -- [EMAIL PROTECTED] http://www.analytics.washington.edu/ Biomedical and Health Informatics University of Washington Biostatistics, SCHARP/HVTN Fred Hutchinson Cancer Research Center UW (Tu/Th/F): 206-616-7630 FAX=206-543-3461 | Voicemail is unreliable FHCRC (M/W): 206-667-7025 FAX=206-667-4812 | use Email CONFIDENTIALITY NOTICE: This e-mail message and any attachme...{{dropped}} ______________________________________________ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-devel
