sui-build

To build and test a Sui Move package, compile the modules using sui move build to validate types and resource safety, then execute unit tests and multi-transaction scenarios with sui move test to verify execution logic.

Yes, you can target specific network environments during the Sui Move build and test processes by using the --build-env flag when your Move.toml configuration defines multiple environments for deployment.

The best way to debug Sui Move test failures is to use trace debugging, print variable values during test execution, and replay past transactions locally to pinpoint execution issues and resource safety violations.

You generate and inspect Sui Move code coverage by running the coverage command to produce module-level coverage reports, verifying which execution paths and resource operations your unit tests successfully exercise.

Yes, Move Analyzer integrates with Sui Move packages to provide faster iteration and development feedback, enabling features like code inspection and type checking directly within supported environments such as VS Code.

A Sui Move build fails with resource safety errors when the compiler detects violations in how digital assets are moved or copied, requiring you to fix module type definitions and resource operations before testing.