Feature Request: Add Support or Guidelines for Automated Testing in CI/CD (e.g., GitLab CI)

[mhetru]

Hello,

I would like to know if there is a recommended way to test a SQLPage application in a CI/CD pipeline, similarly to unit or integration tests.

Our goal is to prevent broken commits from being deployed. Ideally, we would like to:

• Include a lightweight or mock database (with sample data) directly in the repository
• Spin up SQLPage in a temporary Docker environment during CI execution
• Run automated checks (e.g., using curl) against key application pages
• Optionally expose a dedicated “test” page that aggregates important queries or features
• Fail the CI pipeline if any of these checks return an error (non-200 HTTP status, invalid output, etc.)

This would act as a basic quality gate to ensure the application is functional before deployment.

Does SQLPage provide (or plan to provide):

• Built-in support for testing or validation?
• Best practices or examples for CI/CD integration?
• Any recommended tooling for this kind of validation?

Thanks in advance for your help!

Best Regards!

[kryskool]

For automated test, i use httpYac

[lovasoa]

Hi!
Indeed this is a blind spot of the current documentation! I'll work on it when I get the time. I'll probably recommend hurl for individual page tests and playwright for end to end testing.

You can see how we do it ourselves here : https://github.com/sqlpage/SQLPage/tree/main/tests/end-to-end

For spawning databases, I'd recommend docker compose, both locally and on CI.