Rohan Kumar 065e7ad9ad CatmullRomCurve3: Geometry corruption on 2-point curves. (#33270) 2 weeks ago
..
addons 374209b928 Hdr loader header parse fix (#33174) 1 month ago
src 065e7ad9ad CatmullRomCurve3: Geometry corruption on 2-point curves. (#33270) 2 weeks ago
utils d516ced437 Cleanup: remove jshint remnants (#32885) 2 months ago
README.md adfc785952 Test: Remove servez reference. 3 months ago
UnitTests.html 138769ec01 Update UnitTests.html (#25407) 3 years ago
three.addons.unit.js 374209b928 Hdr loader header parse fix (#33174) 1 month ago
three.source.unit.js 91117d008d WebGPURenderer: Fixes framebuffer caching with multiple references of different sizes (#32690) 1 month ago

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 node utils/server.js (or run any other local web server) from the root folder and access http://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, further 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.

粤ICP备19079148号