Running unit tests and integration tests

[GoogleCodeExporter]

Great library. How to run the tests?

Original issue reported on code.google.com by mart...@enketo.org on 11 Mar 2015 at 6:03

• Add a method to run the integration tests.
• Add a method to run the unit tests.

[Dominator008]

Internally at Google, the tests are run with Bazel using rules similar to those in https://github.com/bazelbuild/rules_closure. I will see if those rules can be used to run the tests in this project.

[ScottFreeCode]

Is the difference between the test.js filename and test_js_deps.js referenced in the pages significant?

[Dominator008]

@ScottFreeCode Yes they are different. test.js contains the utilities for running the tests, while test_js_deps.js is an automatically generated file specifying what to goog.require. Unfortunately I don't have access to this file now. Even if I did, I don't think it can be added to the repository easily. For now, I guess you can comment out the line

<script src="./test_js_deps.js"></script>

, see what namespaces are missing, and include them manually.

[ScottFreeCode]

Alright, finally got it working; thanks!

[Dominator008]

@ScottFreeCode Good to hear!

[bedney]

I'm still a bit confused here. So is there a way to run the tests automatically out of the box or do we have to run them one at a time? Is there additional software to install? If so, can it be added to the devDependencies and the gulp file updated so that it can basically be a single command to run all tests?

[Dominator008]

@bedney I'm working on a workflow that will allow running tests out of the box.