Update grunt / jasmine testing framework to support external build

[aashish24]

No description provided.

[jbeezley]

I have an experimental revamp of the unit testing framework here: https://github.com/OpenGeoscience/geojs/tree/fix-build-testing

It allows you to do for example:

cmake -DBUILD_GEOJS_TESTING=ON ${GEOJS_SOURCE_DIR}
make
ctest

The jasmine tests are added as individual ctest targets. The method for doing this was ruthlessly stolen from @ronichoudhury's code in Kitware/tangelo.

[jbeezley]

This, #31, and #19 are all related, so I'm pinging them here.

I updated fix-build-testing to fix the server port issue. I also added an option for node path in the CMakeLists. Grunt expects node to be in the PATH, so I am just adding the given path to the environment variable for each test. A little ugly, but it seems to work.

[waxlamp]

Ruthlessness appreciated :)

Let me know if you run into problems with the general setup, or if you come
up with enhancements etc.

On Tue, Apr 8, 2014 at 11:10 AM, Jonathan Beezley
notifications@github.comwrote:

I have an experimental revamp of the unit testing framework here:
https://github.com/OpenGeoscience/geojs/tree/fix-build-testing

It allows you to do for example:

cmake -DBUILD_GEOJS_TESTING=ON ${GEOJS_SOURCE_DIR}
make
ctest

The jasmine tests are added as individual ctest targets. The method for
doing this was ruthlessly stolen from @ronichoudhuryhttps://github.com/ronichoudhury's
code in Kitware/tangelo https://github.com/Kitware/tangelo.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/40#issuecomment-39859737
.

[jbeezley]

As it turns out we need to use selenium for webgl support, so I am running the tests now through a grunt plugin, grunt-webdriver-jasmine-runner, rather than phantomjs.