eiriklegernaes 7a62164566 WebGLRenderer: Sort objects in clip space. (#28571) 1 anno fa
..
addons 9e0001029f #28440 Fixed BufferGeometryUtils.mergeVertices to handle morphAttributes (#28441) 1 anno fa
src 7a62164566 WebGLRenderer: Sort objects in clip space. (#28571) 1 anno fa
utils df58df8744 Bump metadata.version from toJSON functions to 4.6. (#26026) 2 anni fa
README.md f9ae989944 Documentation: Update "Installation" guide with clearer guidance on build tools and CDNs (#25468) 2 anni fa
UnitTests.html 138769ec01 Update UnitTests.html (#25407) 2 anni fa
three.addons.unit.js 9e0001029f #28440 Fixed BufferGeometryUtils.mergeVertices to handle morphAttributes (#28441) 1 anno fa
three.source.unit.js 07ec4e8e1f WebGLRenderer: Remove WebGL 1 support. (#27836) 1 anno fa

README.md

Setup

  • Execute npm install from the root folder

Run

You can run the unit tests in two environments:

  • Node.js: Execute npm run test-unit from the root folder
  • Browser: Execute npx servez -p 8080 --ssl (or run any other local web sever) from the root folder and access https://localhost:8080/test/unit/UnitTests.html in a web browser.

See Installation for more information.

Notes

A small number of tests can only be run in a browser environment.

For browser tests, futher changes to the library will not be reflected until the page is refreshed.

Troubleshooting

When adding or updating tests, the most common cause of test failure is forgetting to change QUnit.todo to QUnit.test when the test is ready.

An error that indicates "no tests were found" means that an import statement could not be resolved. This is usually caused by a typo in the import path.

Debugging

To debug a test, add debugger; to the test code. Then, run the test in a browser and open the developer tools. The test will stop at the debugger statement and you can inspect the code.