Running unit tests and integration tests about wicked-good-xpath HOT 9 OPEN

@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.

from wicked-good-xpath.

(I mean without opening each html file in /test). I'm wondering if there is a 
way to run all of them at once, in phantomJS ideally.

Original comment by [email protected] on 12 Mar 2015 at 3:19

• Added labels: ****
• Removed labels: ****

from wicked-good-xpath.

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.

from wicked-good-xpath.

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

from wicked-good-xpath.

Alright, finally got it working; thanks!

from wicked-good-xpath.

@ScottFreeCode Good to hear!

from wicked-good-xpath.

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?

from wicked-good-xpath.

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

from wicked-good-xpath.

@Dominator008 - Thank you sir! I appreciate it!

from wicked-good-xpath.