dynamicbible/test/all.js

require('./ref-tests.js').init(exports);
require('./data-quality-tests.js').init(exports);

if (module == require.main) require('test').run(exports);
Split out the unittests into separate files. We use nodes require so we have to follow nodes module conventions for test suites. * As a result we need to inject the requirejs loader as well as the exports object. * Also we need to move the requirejs setup logic into it's own module for reuse. * The test modules add tests to the exports object for our test runner. 2013-11-16 15:26:49 -05:00			`require('./ref-tests.js').init(exports);`
Add some data integrity tests. * Add new test suite test/data-quality-tests.js * Make ParseBook exported so I can use it to get data for each book This is suboptimal since really the data should be in a look up table somewhere but I don't want to tackle that in this change. * Actually load the json data for each book and test that number of chapters exists. 2013-11-16 16:18:36 -05:00			`require('./data-quality-tests.js').init(exports);`
Setup unit testing infrastructure using npm * Add package.json to tell npm what dependencies we need. * Use npm's test package for the assertions * Add a test/all.js as our test suite entrypoint. * Port biblerefparsing tests over to the new unit test framework. 2013-11-16 13:27:56 -05:00
			`if (module == require.main) require('test').run(exports);`