dynamicbible/package.json

{
    "name": "dynamicbible",
    "description": "DynamicBible Dynamic HTML javascript",
    "dependencies": {"requirejs": ">=2.1.9"},
    "scripts": {"test": "node test/all.js"},
    "files": ["./js"],
    "devDependencies": {"test": ">=0.0.5", "cjson": ">=1.0.0"}
}
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			`{`
			`"name": "dynamicbible",`
			`"description": "DynamicBible Dynamic HTML javascript",`
			`"dependencies": {"requirejs": ">=2.1.9"},`
			`"scripts": {"test": "node test/all.js"},`
			`"files": ["./js"],`
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			`"devDependencies": {"test": ">=0.0.5", "cjson": ">=1.0.0"}`
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			`}`