Testing Framework

[zdfs]

So I'll help write tests. Anyone have an opinion on what they'd like to use? I thought the simplest thing might be Mocha/BDD/JSDOM.

Thoughts. Votes.

[dperrymorrow]

I would be willing to write some tests as well.
If it were up to me I would choose Karma with Jasmine. Purely from the standpoint of thats what I have the most experience with.

Karma will let you test in many different browsers easily which I'm expecting to be important on a project like this.

http://karma-runner.github.io/0.13/index.html

[zdfs]

I don't mind Karma, I just hate configuring it. You want to pick up that part?

[dperrymorrow]

sure thing, karma works great with mocha too, wanna use that instead of Jasmine?
Just have used Jasmine more, but open to using Mocha. Heard good things.

[zdfs]

Yeah. I like Mocha more than Jasmine. But either way works. I've used them all at some point. The syntax will basically be the same.

[dperrymorrow]

there ya go...

[lipis]

Would be nice to setup TravisCI as well..

[LeaVerou]

You guys rock, thanks!
And yes, I will set up TravisCl once we have some tests :)

[dperrymorrow]

👍 for sure, would be nice to see that tests are passing on pull requests.

[LeaVerou]

Hmm, anyone has any idea why Travis doesn't seem to be working? I activated this repo on travis-ci.org, I added a .travis.yml file, nothing… What did I forget?

[zdfs]

@LeaVerou I'm wondering if it's because there's nothing in the master branch. Could be that we need to tell Travis that we're not using master somehow?

[zdfs]

Try something like?

# whitelist
branches:
  only:
    - gh-pages

[zdfs]

Ah. Here we go. Seems like this is the official answer. http://stackoverflow.com/questions/12878568/travis-ci-triggers-build-only-for-master-branch-in-github-repo

[zdfs]

Ok. We have builds and a testing framework. Closing this out. We should probably make individual issues for needed tests.