Streamlining Drupal End-to-End Testing with Docker, JSON-RPC, and GitHub Actions

Staff Reporter

female-freelance-developer-coding-html-script-with-online-cloud-server-programming-firewall-security-learning-new-user-interface-terminal-window-with-code-language-application — DCStudio / Freepik

Prabashwara Seneviratne details how Nuvole implemented efficient end-to-end (E2E) tests for ILO Live, a headless Drupal–Next.js platform. The team used a private JSON-RPC API to dynamically configure Drupal test states and a custom Docker image to speed up environment setup. This enabled rapid, realistic E2E testing, including live-stream simulation via AWS AppSync.

Key innovations include using JSON-RPC to create and reset content during tests, and replacing MariaDB with SQLite in Docker to accelerate CMS startup. Tests were integrated into GitHub Actions using Cypress, and custom Cypress commands streamlined API calls and page validations.

Over 50 tests now run in under eight minutes, providing reliable validation of critical features like live events. This approach not only increased test speed but also simplified developer workflows. The post offers concrete, reproducible strategies for other teams adopting Drupal as a backend in decoupled architectures.

Reference: Implementing Fast End-to-End Tests on Drupal With Docker and JSON-RPC by Prabashwara Seneviratne, Nuvole (7 July 2025)

JSON

Docker

Cypress

Headless Drupal

DevOps

Drupal Automation

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.