Mr.doob adfc785952 Test: Remove servez reference. 4 dienas atpakaļ
..
addons 5aea7c6768 Global: Clean up. (#32519) 1 mēnesi atpakaļ
src 877da70678 WebGLRenderer: Consider skinning / instancing when sorting objects. (#28125) 3 nedēļas atpakaļ
utils 5aea7c6768 Global: Clean up. (#32519) 1 mēnesi atpakaļ
README.md adfc785952 Test: Remove servez reference. 4 dienas atpakaļ
UnitTests.html 138769ec01 Update UnitTests.html (#25407) 2 gadi atpakaļ
three.addons.unit.js 57decfe0bd Tests: Add test for USDZExporter (#31435) 5 mēneši atpakaļ
three.source.unit.js 6a0dab07a3 BatchedMesh: Fix `setInstanceCount()`. (#31458) 5 mēneši atpakaļ

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号