Testing and Continuous Build?

[dglazkov]

Traceur seems to have nice build status and everything. I have no idea how to do this, but would love me summodat.

[arv]

It is Node.js tests using mocha+chai, set up to work with TravisCI

[mereskin-zz]

And probably you would want to use Karma runner, to run tests on actual browsers. PhantomJS is a little bit outdated, it doesn't support MutationObservers and CustomEvents have to be polyfilled, for example.

[dglazkov]

@domenic, do you have any experience with Karma or any of this stuff?

[dglazkov]

I'd say this should be prerequisite to writing any more code -- can't write code without writing tests 😃

[mereskin-zz]

I'd be happy to help, if yo've got time to give me a heads-up.

[dglazkov]

@mereskin any help and/or pull requests are appreciated. At this point, we can state the task minimum as "set up a run test/index.html and report some result, on one browser, for every commit." We can grow it from there 😃

[mereskin-zz]

#16

[dglazkov]

Thanks, @mereskin!! Sadly, @arv and I just realized that there's no easy way to run Karma on a CI server like travis-ci. @arv is trying the testling thing now...

[mereskin-zz]

I believe it is possible. I will look into it when I get home

[arv]

Based on my very limited research travis only support Firefox and PhantomJS.

[mereskin-zz]

They say they have Chromium, too: travis-ci/travis-ci#2281

[dglazkov]

@mereskin cool! Do you know what version? Ideally, would love to run 35+, so that we don't have to polyfill shadow DOM and custom elements. @arv got testling to work, but their browsers are somewhat stale.

[mereskin-zz]

Don't know, unfortunately, haven't used it yet. Worth checking.

Is polymer's CustomElements polyfill + Firefox combination completely irrelevant? So far it helped me, but I haven't done anything hardcore.