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.

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

Automated testing #72

Closed
7 tasks done
jeromesimeon opened this issue Sep 8, 2017 · 2 comments
Closed
7 tasks done

Automated testing #72

jeromesimeon opened this issue Sep 8, 2017 · 2 comments
Labels

Comments

@jeromesimeon
Copy link
Member

jeromesimeon commented Sep 8, 2017

We should provide tests for various source and target languages. The ./samples directory could provide an initial set of tests. A first push toward testing would involve:

  • Separate runners from samples
  • Check that the -output option on the command line properly checks for the expected result and returns success and failure properly.
  • Add expected outputs for the sample queries in ./samples
  • Provide a proper make test target that run the tests in ./samples
  • Fix the way testing reports results so it's readable
  • Come up with a reasonable first set of tests
  • Add tests for backends
@jeromesimeon jeromesimeon mentioned this issue Sep 15, 2017
8 tasks
@jeromesimeon
Copy link
Member Author

There is a first set of tests in ./samples. The test target currently only uses internal eval. We should expand that to include tests for the various backends (JavaScript, Java, Cloudant, Spark).

@jeromesimeon
Copy link
Member Author

Some form of testing is essentially done, including for JS and Java backends. Those are now run through CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant