db_manipulation_testing

To test game logic via database manipulation, load the `cards_compiled.json` file, convert it to a `CardDatabase`, and modify abilities or card data directly in memory before simulating the game state. This allows you to isolate and test specific mechanics easily.

You can test specific card abilities without triggering in-game conditions by overwriting the card ability bytecode directly in the in-memory database. This isolates the mechanics, bypassing complex prerequisites and focusing on the targeted rule or edge case.

The best way to unit test individual opcodes and bytecode logic is by calling the interpreter directly. This approach allows for deterministic testing of specific game engine components without running the full event pipeline.

Yes, you can simulate end-to-end gameplay to test suspensions and responses by enqueuing abilities and stepping through the game loop. This full event pipeline testing ensures all game engine components interact correctly.

Database manipulation testing works effectively for testing broken mechanics and edge cases. By dynamically overwriting card abilities and bytecode in memory, you can reproduce specific scenarios and verify complex rules deterministically.

Yes, you need to create a new test file in the `engine_rust_src/tests/` directory, such as `repro_example_test.rs`. This is where you define your data-driven QA verification tests by manipulating card abilities in memory.