Additional Considerations
Last updated
Last updated
When testing the WASM bundle, which contains the core game logic, focus on:
Testing State Machine Transitions: Verify that the game handler transitions between different game stages correctly in response to various events.
Validating Event Handling Logic: Test the logic within the handle_event function to ensure that it processes events correctly, updates the game state as expected, and generates appropriate effects.
Testing Randomness Generation: If your game uses randomness, test the interaction with the to ensure that randomness is generated and revealed correctly and securely.
Testing Settlement Generation: Verify that the game handler generates accurate and fair settlements based on the game outcome and player states.
When testing the client-side integration with the , there are some additional considerations:
Mocking Blockchain Interactions: Since the client-side code does not directly interact with the blockchain, you may need to mock blockchain interactions during testing. The test kit provides utilities for creating mock game accounts and simulating blockchain responses.
Testing Decryption Logic: If your game involves hidden knowledge and decryption, make sure to test the decryption logic in your client application to ensure it functions correctly and securely.
Simulating Network Interruptions: Test how your client application handles network interruptions and reconnects to the Transactor server to ensure a smooth gameplay experience even in the face of network issues.
By utilizing the Race test kit and following best practices for unit and integration testing on both the WASM bundle and client sides, developers can build robust, secure, and fair blockchain games on the Race Protocol infrastructure.