Improvement/add test runner #42
Reference in New Issue
Block a user
No description provided.
Delete Branch "improvement/add-test-runner"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Don't know if this is imposing, but I thought testing may be easier if there was a more manageable way to run them. Also, the added benefit is that when ready to test this in other browsers, karma launchers for them can be added to the package.json & karma.conf.js. What do you think?
also, the specs in Layout-random-test.js seem to be failing:
is this a known issue?
Nice, thanks for doing that :) Never used karma, this looks sweet. For the failing tests, there's a few behaviors which I believe are bugs in Chrome.
https://github.com/facebook/css-layout/blob/master/src/tests/Layout-test.js#L1117-L1119
https://github.com/facebook/css-layout/blob/master/src/tests/Layout-test.js#L1176-L1178
And, there's a few edge cases that are not properly supported yet unfortunately :(
Ah I see...well np anyways. Glad to help.
Question: what do you think about adding a linter (like jshint) to the npm pretest script so that the JS files get linted before tests get executed?
Also, good job on Reactjs Conf, the presentation on native looked super cool!
Happy to take it in, however i'm doing a lot of hacks that are probably not eslint friendly :p