From: James F. <jam...@ex...> - 2010-07-10 14:12:33
|
FYI: I commited a bunch of xquery level unit tests under test/src/xquery/util/util.xml for the util module which further demonstrates how developers should test their xquery functions using the xquery test library which for those who do not know, is now enabled by default in conf.xml (in trunk version) ala <module src="resource:org/exist/xquery/lib/test.xq" uri=" http://exist-db.org/xquery/testing"/> Its simple to use and provides us with an ability to test xquery consistently across core and extensions ... I think we probably need to have a discussion at some point about rationalizing the test directory (for example where should unit tests go for xquery extension modules). I know that this may seem a little strange (if not slightly masochistic) to add unit tests for existing functionality but I see this kind of activity as important to imparting robustness to eXist especially as we are constantly refactoring and adding/changing things. I would ask that existing extension developers consider adding xquery level unit tests to their work. Another consideration is if we are to run xquery unit tests as part of default core tests. Perhaps we can make a mention of using the xquery test library in the various developer / manifesto docs. James Fuller |