feat(gen): unify testing framework

[kingcody]

Changes:

• add prompt for Jasmine or Mocha
• if Mocha choosen, prompt for Expect or Should
• use <%= does() %> to dynamically insert assertions (expect|should)
• add mocha variants for protractor tests
• add mocha options to protractor.conf
• remove test/fixtures/(bower|package).json from repo
• move runE2E functionality to runTest and simplify switch
• comment generator test functions

Note:
Server-side jasmine test are needed to fully unify testing frameworks.
Once Jasmine tests are included for server, mocha dep can be removed
fully when selecting Jasmine.

[kingcody]

@JaKXz, I know you don't have a lot of extra time, but I could use some server side Jasmine tests to match the ones written in Mocha. Even a 'call' for tests would help, especially coming from a 'collaborator'.

I need to adjust timeouts for protractor/mocha, but other than that; this PR simply lacks server side Jasmine tests.

My main issue is the differences in flow control such as before, beforeEach, after, afterEach. I'm not sure how to structure the before clauses in Jasmine. Also I'm pretty busy with several client's ATM, but I'll try to do what I can. Just wondering if I might be able to get some help on this one. Thanks.

[JaKXz]

@kingcody I hear you, committing to get you a PR on your feature branch soon.

Those who are familiar with Jasmine, please feel free to contribute as well.

[DaftMonk]

Updated the travis config so e2e tests should run on pull requests now. You'll need to merge canary back into your branch.

Edit: actually I spoke to soon, need to work on this a bit more to get it working for pull requests

[kingcody]

My apologies, I should have mentioned the build issue is a WIP. I'm currently working on an issue with karma and url.parse. Also, the last e2e test set that uses jasmine and no server ops is failing in an odd way, perhaps it might be clearer to you?

[DaftMonk]

@kingcody Ok I just had to fix the credentials for sauce labs in the .travis.yml. Travis wasn't building pull requests with sauce labs, for running the protractor tests. Not sure why only one set of e2e tests was failing though, they all should have failed.

[kingcody]

Odd indeed; I'll rebase and test when I get back to my computer. Do you have a preference on handling the node 0.11.14+ issue with the build process? I was going to specify 0.11.13 in travis.yml for the time being and continue to work on the url.parse issue and follow the karma issue thread.

[DaftMonk]

I'm totally fine with specifying 0.11.13 until that issue is fixed.

[kingcody]

Sounds great, I'll try to get this patched up tonight.

Side note: Once the issues are sorted out this PR will work without Jasmine server test. I tried to set it up nicely to be able to drop them in and adjust the dependency conditionals. It's up to you if you'd like to go ahead and merge or wait for the jasmine tests. I'm perfectly content either way.

[kingcody]

Not sure whats up with the sauce labs tunnel connection on this build, but everything works fine on my Travis build, same commit hash...