Initial Karma Support

[ggetz]

Added Karma support as a first step for integrating tests as part of Travis-CI build process.

• Added Karma and necessary karma plugins to package.json, including launchers for:
  • Chrome
  • Firefox
  • IE
  • Safari
• Configured Karma to run jasmine tests
• Added test and test-all targets to gulpfile.js
  • test runs karma tests using browser specified in config file, currently Chrome
  • test-all runs karma tests using all browsers available

TODO

• Add back in minified release and webGL validation support.
• Update wiki for new test targets (categories and the two above)

Post merge
See #3571

[pjcozzi]

Exciting! Can you please update any of the related Contributor's Guides in this branch?

[mramato]

Does it also need to work for the it function?

It looks like the original code just uses defineSuite and describe, so I think we're good.

[ggetz]

@mramato Also I didn't mean to do that merge, can I undo it somehow?

[ggetz]

It looks like the original code just uses defineSuite and describe, so I think we're good.

OK

[mramato]

I'll stop by.

[mramato]

This is almost ready, I'm probably going to make some final tweaks (hopefully tonight) to better fit normal cesium dev workflow and then I'll merge. Thanks @ggetz.

[ggetz]

Awesome, thanks @mramato

[mramato]

This PR just got more awesome. Building on @ggetz great work, I added Electron as a launcher option and set it to run headless. I then make it the default when running via WebStorm's own Karma runner. This means you can now run the tests from WebStorm with no additional windows or pop-ups and WebStorm presents the test in an easy to read tree with per-test output logs and clickable callstacks when things go wrong.

@pjcozzi and @ggetz would you might syncing this branch and giving it one last try. After running npm install and opening WebStorm, you'll have a Run tests option in the upper right:

Give it a try and let me know what you think.

[pjcozzi]

Works great. fit is also great. Is there anything like that for an entire suite we can add for our defineSuite since we (at least, me) often run tests for a suite at a time?

[pjcozzi]

Also, add this to the test guide if you didn't already.

[mramato]

defineSuite does not exist in Jasmine, I'm not sure of the history as to why Cesium has it's own thing here instead of just using Jasmine describe directly (it's probably worth looking into). That being said, adding fdefineSuite should be easy.

[ggetz]

This works great! Very cool!

[pjcozzi]

I think the defineSuite history is AMD-related, but you would know better than me.

[mramato]

Okay, fdefineSuite is in and I updated the guides to include both new options as well as a quick Webstorm testing guide.

I also added a --browsers option for specifying browsers on the command line, i.e. npm run test-webgl --browsers Firefox,Safari will run web-gl only tests against Firefox and Safari.

[mramato]

While I'm sure there are plenty of kinks to work out, I think this is a huge step up for our dev workflow and is ready for master. Since I did a bunch of work with @ggetz, I probably shouldn't be the one to hit merge; so @pjcozzi please do the honors when you are ready.

[pjcozzi]

👍

[mramato]

@kring you are no longer a liar. You can thank @ggetz for it.

Thanks again @ggetz

[ggetz]

Thanks @mramato !

[kring]

Yay! Thanks @ggetz! :)