dojo-test

Dojo tests for Cairo models and systems use spawn_test_world setup, world.read_model and world.write_model_test assertions, and optional should_panic checks to validate game logic and state transitions. Tests require #[cfg(test)] guards and proper model registrations.

spawn_test_world is used in Dojo integration tests to scaffold test world setup with namespace and contract definitions. It enables multi-player flow testing by spawning players and validating model state changes through system interactions like movement and actions.

Cheat codes like set_caller_address, set_block_timestamp, and set_contract_address simulate different execution contexts in Cairo tests. They enable multi-player test scenarios and verify permissioned model interactions within Dojo systems.

Permissioned model interactions in a Dojo world are tested using world.sync_perms_and_inits along with world.read_model, world.write_model_test, and world.erase_model assertions. These verify state transitions and enforce access control for system actions.

Unit tests belong in model files with #[cfg(test)] guards, while integration tests go in a separate tests directory. Integration tests use spawn_test_world setup for full system validation, and unit tests focus on individual model logic.

After spawning a player and calling the actions system, assert Position and Moves model updates using world.read_model calls. Verify the move system updates Position coordinates and decrements Moves count within the test world environment.