dojo-integration-test

Running local Dojo integration tests requires provisioning a complete development stack including Katana, Torii, and the Cairo contract project. The test workflow automates setup, migration, deployment, and runtime interaction for reproducible end-to-end verification.

Setting up a local Dojo testing environment requires installing asdf plugins for sozo, katana, torii, and scarb. You also need an existing Dojo project with the correct structure and available ports to run the local development stack components.

Verify Dojo contract behavior by provisioning the local stack, migrating contracts, and launching Torii. This enables end-to-end verification through world state inspection and querying the runtime state via GraphQL and GRPC endpoints.

Yes, the Dojo integration testing workflow automates contract migration and deployment. It provisions the local development stack to ensure contracts are deployed repeatably before executing runtime interaction and verification tests.

If your local Dojo testing stack is not working, verify that the required ports are available and not conflicting. The guided startup sequence performs port checks and validates that all prerequisite tools like Katana and Torii are running correctly.

You need end-to-end integration testing for Dojo development when automating reproducible test workflows for Cairo contracts. It provisions a local stack to test deployment, migration, and runtime interaction scenarios comprehensively.