Automated Testing the game

[luchillo17]

I see 2 levels of testing when a game is involved:

1. Unit testing game utilities: Testing rendered behavior like collisions under specific circumstances usually doesn’t qualify as Unit Testing, so here I believe it lands only the testing of utility functions, for example with Jest one would not test the canvas, instead one would mock the canvas, maybe mock the part of the engine that renders the game and then test the state of the game after certain actions?

2. Integration testing: Usually implies running an actual render of the web page, executing actions against the app like button clicking, and in this context, actions on the canvas like clicks and keyboard inputs, then asserting the expected state of the app or canvas after given actions.

Here are my questions:

1. It seems like the Phaser 3 community has no rush to define a standard for automated testing of the game (I can only hope the Phaser 4 in the works will add features or guidelines aimed at this).

2. I hope someone has examples of automated testing since other threads related to this topic have broken links.

3. Why am I in such need of automated testing? well it was requested by a potential employer, yes there are companies out there seriously considering Phaser 3 as a game engine, and they want testing, has anyone else stumbled into this kind of situation?

Lastly, the few resources I could find in this forum, as well as an NPM library that seems to try to address this:
phase-2-e - npm (npmjs.com)

Unit Testing

Whatever you do, listen to @jorbascrumps . Do not attempt 100% coverage. If I were in your position, I’d just isolate whatever code I can unit test, and well, test it (using jest, etc). The thing to look for is long functions (with more than, say, 30 lines of code or nested if statements). Try to extract that code into smaller functions that you can unit test. That way, your create/update methods are relatively clean e.g: // file1: probable a scene class create(){ this.thingies = longProce…

E2E Testing with Phaser & Cypress

Thought I would share this out here for anyone that might find it useful. I recently demoed using Cypress to perform targetted, isolated E2E tests of a game built with Phaser. [main-gif] Check out why I wanted to do this and how I did it below.

This one has broken links so not so useful…

Guidelines, best practice and Testing Template

Not a “best practice” by any means, but in the development of my game I have two types of tests: unit testing for game logic that can be ran server side e2e testing for game behavior, from the user’s point of view (acceptance testing) here’s one example mana-battle/specifications.spec.ts at master · lfarroco/mana-battle · GitHub the tests run on every commit and are good to catch regressions (here’s one example run Merge pull request #106 from lfarroco/dependabot/npm_and_yarn/babel/core-7.16…

In the examples, there’s a tester/index.js which is using puppeteer in some capacity, but I only see it as testing if a canvas is there, I don’t see any game assets or logic tests:
examples/tester/index.js at master · phaserjs/examples · GitHub