Add sanity checker.
Travis
Show number of tests found
Minor formatting (and get travis to build)
Update README.md

Added travis status image
Update README.md

Travis status for develop branch
Add sanity check to validate all suites against suite schema.
Make sure optional test suites don't skip the sanity checks.
Add back executable bit to suite_sanity_check
Merge pull request #17 from gazpachoking/validate_suite_content

Add sanity checks for actual format of test suites
Add a test for BigNum integers.

Closes #12
Added name to license.
Added tests differentiating between lexical and mathematical integers.

Integer literals should be considered integers, while mathematical integers can
be specified with divisibleBy.

See: https://github.com/json-schema/json-schema/issues/27

Closes #2
Cleanup

* Make errors in the tests be failures
* Removed use of ErrorTree
* Added another helper fn
* Use fnmatch instead of glob
Tag version 1.0.0.

Closes #13
json-schema-validator also uses the suite

Heck, most data in it came fom this project's test files to begin with!
Move "1.0 is not an integer" to the optional tests section

Thanks to some brain damaged languages, and given what section 5.5 says, this
test has to go in this section.

What on earth was ECMA thinking, I wonder.

Solves issue #22.
Fix syntax error in newly created test
Rename "1.0 is not int" test to a more meaningful name

I am overreacting on such matters.

See issue #22.
Changed ridiculous test description.
patternProperties: check regex engine matching more completely

* Regex matches are not anchored.
* Matching is case insensitive.