insites-unit-tests

To write reliable Liquid unit tests for Insites applications, you need to initialize and return the testing contract, place files under app/lib/test with an _test.liquid suffix, and use approved assertion functions for validation.

Unit tests for Insites should cover commands, validators, queries, authorization rules, helpers, and background jobs, ensuring you test happy paths, validation failures, missing records, and edge cases.

To execute Liquid unit tests, you must deploy your application to the staging environment first, then run the tests using the platform's repeatable test execution procedures after ensuring correct file placement.

Insites unit testing supports assertion-driven validation functions that map requirements to equality, presence, validity, and boolean checks to verify contract compliance for your components.

Yes, Insites unit testing requires a specific file naming convention where test files must be placed under the app/lib/test directory and named with an _test.liquid suffix to be recognized.

Insites unit tests fail during execution if the testing contract is not properly initialized and returned, files are incorrectly named or placed, or the application has not been deployed to staging.