Claude
91043c09d9
Resolve the conflict in the in-game editor: keep the TransformControls helper (Three.js r169+ API) and the world scale on it, and apply the new patch removing the axis guide lines. Also adapt code added on master to the upgrade: - Add the renderer3DWorldScale to the scene data of the new PhysicsCharacter3D test. - Give Source its type argument, now required by @types/three. - Rename the @types/three patch to the installed version (0.185.1), so patch-package stops warning about it. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01HdyuCYDD8w7U2Q3p1aHY5M
These are the tests for the GDevelop JavaScript game engine.
Launching tests
Make sure you have Node.js installed. Update dependencies:
cd GDJS/tests
npm install
Then launch tests:
npm run test:watch # This will use Chrome Headless
npm run test-benchmark:watch # This will also run benchmarks
npm run test:firefox:watch # To run tests using Firefox
⚠️ If you're working on GDJS or extensions, make sure to have the development version of GDevelop running so that changes in GDJS or extension files are rebuilt (or run
npm run buildinGDJS/, but better run GDevelop so that any changes are watched).
About the tests
Unit tests
Tests are launched using Chrome. You need Chrome installed to run them. You can change the browser by modifying the package.json "test" command and install the appropriate karma package.
Tests are located in the tests folder for the game engine, or directly in the folder of the tested extensions.
Games in the games folder
Games contained in the games folder are mainly here to be launched manually to check that a particular feature is working. Read the comments in the events to see what is the expected behavior, or compare with the native platform if you can.