Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Run json-schema.org's common test suite #122

Merged
merged 5 commits into from Oct 26, 2014
Merged

Run json-schema.org's common test suite #122

merged 5 commits into from Oct 26, 2014

Commits on Sep 18, 2014

  1. Run json-schema.org's common test suite

    @mpalmer
    mpalmer committed Sep 18, 2014
    Copy the full SHA
    a6793f2 View commit details
    Browse the repository at this point in the history

  2. Init/update submodule as required

    @mpalmer
    mpalmer committed Sep 18, 2014
    Copy the full SHA
    1a4bdd4 View commit details
    Browse the repository at this point in the history

  3. Switch to inferior indent scheme

    @mpalmer
    mpalmer committed Sep 18, 2014
    Copy the full SHA
    ff649e3 View commit details
    Browse the repository at this point in the history

Commits on Sep 19, 2014

  1. Display *why* a common-test-suite test failed 

    This is good, because it's easier to debug a problem if you know *why*
there's a problem.
    @mpalmer
    mpalmer committed Sep 19, 2014
    Copy the full SHA
    a247e28 View commit details
    Browse the repository at this point in the history

Commits on Oct 25, 2014

  1. Skip tests that we know fail, rather than not defining them 

    As suggested by @pd.
    @mpalmer
    mpalmer committed Oct 25, 2014
    Copy the full SHA
    d83f18e View commit details
    Browse the repository at this point in the history