Florian Rival
44ba8a04ce
A gameplay test plays a game: it presses keys, moves the mouse, touches the screen, then checks that what should happen actually happens. For example, if the coin is collected, the score goes up, the enemy hurts the player... Tests run in a preview of the game, usually much faster than real time. [Read more about them on this page](https://wiki.gdevelop.io/gdevelop5/interface/gameplay-tests/)
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.