Developer guide

Run tests and site checks

Use the project's test workflow in a dedicated development or test environment. Two CLI entry points have different scopes:

  • runtests starts the configured test runner and accepts test selections.
  • sitetest garden stops the site, drops and uses the z_sitetest database schema, runs site tests, then restarts with normal configuration. Use a disposable test environment and avoid concurrent runs sharing the database.

Read the relevant reference page before choosing arguments. Tests may create or change data; a passing startup check is not a complete test of models, permissions, and browser behavior.

Run a focused test for the change, then the repository's required broader checks. Preserve the first meaningful error and reproduce it with a minimal case rather than repeatedly restarting the whole node.

Related documentation

Developer guide

Trace a small number of Erlang calls

Open the Development function tracing tool as the admin user. Enter a module, optionally a function, and a small limit on the number of…

Cookbook

Create a reusable module

Create apps_user/zotonic_mod_garden with the following files. This example adds a discoverable module without starting an extra process.