Test Framework

[jkruder]

Test framework has been created using Karma/Mocha/Chai/Sinon/PhantomJS (SauceLabs for CI is in the works). Tests should be added under the test/ directory. Any test fixtures that you may create should be placed under test/fixtures/. A sample test file has been created verifying some behaviors of the Checkbox component (this is intentionally not complete -- I wanted to get this out to the community so that we can all start contributing tests). Tests will be written in ES6 and transpiled to ES5.

Test coverage is handled by Istanbul. However, Istanbul has a bug that is currently preventing it from generating HTML reports so we'll need to depend upon something that can process the LCOV reports (travis). Test results (pass/fail) and coverage summaries are dumped to the console (a detailed text report is also generated under the coverage\ directory).

To have Karma watch your test files, run npm run test-watch. To perform a single run, execute npm test. If we want to integrate Karma with Gulp, we can do that. I chose not to because it is trivial to run the tests and I did not want to incur the overhead of spinning up/down Karma's server.

Note that a browser-polyfill is required for PhantomJS 1.9.X.

Resolves #396

[hai-cea]

Sweet - thanks @jkruder 👍

[jkruder]

Let there be testing!

[jkruder]

Something I found out the hard way: engine.io-client is a dependency of socket.io-client and engin.io-client has a dependency on an archived git repo. So anyone trying to use material-ui behind a firewall/company intranet may run into some issues. There is a PR to resolve the engine.io-client dependency issue. I can't say when it will be resolved, but hopefully soon.

A workaround: Stand up nexus (>2.10) or some other NPM hosting product and download/obtain the source for engine.io-client and the github dependency. Modify the github dep's package.json and give it a version number (something in the 0.0.X range or even 0.0.0-beta) and then add it to your hosted npm registry. Update the engine.io-client package.json so that the github dep is the version number you selected in the previous step. Upload engine.io-client into your npm registry. Configure your registry so that it serves up the deps that you just loaded before searching other repos. That should temporarily address the issue with Karma until it is resolved permanently