Failing tests (with a clean install of three.js dev)

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.

problem

The three remaining also fail when doing npm run test. They are the following:
euler

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.

The other two failing tests only happen in the browser GUI and are these:
failsonlyinbrowser

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.

Author: Fantashit

1 thought on “Failing tests (with a clean install of three.js dev)

  1. @levilime this is not so much a failing of the tests as a failing of the way you’ve set up your testing environment – every web app that loads files locally would fail in the exact same way in this case.

    A README.md file for the tests is not a bad idea though, it could link to the how to run things locally page.

Comments are closed.