Opened 14 years ago

Last modified 5 years ago

#417 new task

Component integration testing framework

Reported by: Philip Taylor Owned by:
Priority: Should Have Milestone: Backlog
Component: Simulation Keywords:
Cc: Patch:

Description

#415 and #416 are about testing components in isolation, but there should be some automated way to test that the whole gameplay system works together and the components interact properly.

Maybe it would be done by loading a map, sending a pre-defined sequence of player commands, simulating a certain amount of time, and then checking that the outcome is as expected (some units are in certain areas, some are dead, etc, with enough flexibility to allow for tweaks to pathfinding algorithms and unit stats etc without breaking the test results). In case of test failures, it should be possible to watch the simulation and see where it's going wrong.

This wouldn't aim to exhaustively test every aspect of gameplay, since that would require a huge amount of work - it would just test basic functionality, and particular bugs or regressions that we don't want to miss.

Change History (4)

comment:1 by (none), 14 years ago

Milestone: Unclassified

Milestone Unclassified deleted

comment:2 by Andrew, 14 years ago

Milestone: Backlog

comment:3 by historic_bruno, 11 years ago

Owner: Philip Taylor removed

comment:4 by Imarok, 5 years ago

Component: UI & SimulationSimulation

Move tickets to Simulation as UI & Simulation got some sub components.

Note: See TracTickets for help on using tickets.