Test Automation

Test automation in games means tests that run without a person: build smoke tests, regression suites, performance runs and the reporting that makes a failure readable.

The skill combines programming with QA judgement. Writing the suite is the smaller part; deciding what is worth automating is the larger one. Deterministic checks, server and backend tests and anything that has to run on every commit pay back quickly, while a test that depends on timing or rendering output often costs more than it saves.

CI systems run the suites, bug trackers receive the results, and the reporting has to point at the change that caused a failure rather than at the test. Java, Python and PHP appear in the postings alongside the engine language of the project, because much of this work sits around the game rather than inside it.

QA Testing is the human work of playing a build and judging it. Automation takes over the repeatable checks so that the manual effort goes where judgement is actually required.

Where these positions are: Berlin (2 positions), Hamburg (2 positions), Helsinki (2 positions), Bucharest (1 position)