ycw 3e2a3734ee inf. bounds (#25546) 2 سال پیش
..
src 3e2a3734ee inf. bounds (#25546) 2 سال پیش
utils 1ad78ef3dd Tests: Post Update Review (#25417) 2 سال پیش
README.md 0a0cd31364 Docs: CompressedTexture and CompressedArrayTexture image property, Unit test Readme. (#25492) 2 سال پیش
UnitTests.html 138769ec01 Update UnitTests.html (#25407) 2 سال پیش
three.source.unit.js 16ac8654e4 Tests: Unit Tests for Core (#25402) 2 سال پیش

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 How to run things locally 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.