frappe-testing-cicd

Setting up GitHub Actions for a Frappe app requires provisioning MariaDB and Redis services with working health checks and matching bench configuration. This generates a deterministic test flow to create a site, install the app, build assets, and run scoped tests.

Configuring a Python version test matrix for Frappe bench tests involves defining the Python and database versions in your GitHub Actions workflow. This ensures your pull requests reliably run the correct bench setup and catch issues across multiple environment combinations before merge.

A Frappe CI/CD pipeline should include pre-commit, ruff lint and format checks, and ESLint checks for JS and Vue files. Adding Semgrep security scanning with Frappe-specific rules further enforces quality by catching anti-patterns before code is merged.

Yes, you can run parallel test builds for Frappe apps in GitHub Actions. The CI setup generates a standard bench-based test flow that supports parallel test options, allowing you to execute scoped app tests deterministically across your configured test matrix.

Frappe CI testing supports optional PostgreSQL services alongside the required MariaDB and Redis. When configuring your GitHub Actions workflow, you can include PostgreSQL provisioning with health checks to test your Frappe app against multiple database backends.

Frappe bench tests often fail in GitHub Actions CI due to missing service health checks or incorrect bench configuration for MariaDB and Redis. Ensuring health-checked services and a deterministic test flow for site creation and app installation prevents broken pipelines.