Closed eywalker closed 9 years ago
Should we set up a dj_test
schema that exercises all major functions? The tests will assume the availability of the dj_test
schema on the current server. The user should have permissions to it.
Should we try to by default work on test
database to test all its features? Wasn't it the case most database installation comes with fully open test
schema?
I've added test
package as a sub-package in the datajoint
. It is designed to run using nosetest.
I'll continue to add test cases as I go over already implemented features. Also, test cases should be added preferably prior to implementing a new feature. Doing so will make spotting unimplemented features easier and also would serve as convenient entry points for debug.
Implement organized testing scheme. Thinking about using nose.