Some failing tests in a clean install of three.js dev branch
In my local version of the current three.js (eb8f846) five tests fail. Two of these only fail when using the QUnit browser GUI that is generated in
test/unit/UnitTests.html when doing
npm run build-test.
I think these three tests fail relating to a issue with the behavior of
assert.step in Qunit as highlighted here: qunitjs/qunit#1226 . It shows that counting the assert steps is not completely transparent from a test writing perspective.
Because they work when running
npm run test they are less of a priority to fix.
I wonder if it is interesting to fix these, although it seems from previous discussion that they seem to still work for some developers.
To reproduce I suggest to create a clean version of the code base with a clean npm install.
I run npm
5.6.0 and have the windows 10 operating system.