Free, Open Source, Self-Hosted WhatsApp API Gateway
TypeScript apibotgatewayself-hostedwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-gatewaywhatsapp-gateway-apiwhatsapp-webwhatsapp-web-api
docs(ci): name the throttler-redis suite beside queue-on
Yudhi Armyndharis80b303ca4a82
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex 898ce35f9..3830b1a5c 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -132,9 +132,9 @@ jobs:name: Testruns-on: ubuntu-latesttimeout-minutes: 20- # Mirrors ci.yml's test job. The queue-on e2e suite needs this service: under GitHub Actions it- # fails rather than skipping when Redis is unreachable, so the tag is never verified less than the- # branch it came from.+ # Mirrors ci.yml's test job. The queue-on and throttler-redis e2e suites need this service: under+ # GitHub Actions they fail rather than skipping when Redis is unreachable, so the tag is never+ # verified less than the branch it came from.services:redis:image: redis:7-alpinediff --git a/docs/09-testing-strategy.md b/docs/09-testing-strategy.mdindex d7e7ca9d3..d4ca6fa37 100644--- a/docs/09-testing-strategy.md+++ b/docs/09-testing-strategy.md@@ -357,9 +357,9 @@ Live WhatsApp checks require an operator-owned account and should not be part ofsmoke imports Baileys and launches the browser, neither of which needs WhatsApp to be reachable.- The default `test` job uses SQLite; PostgreSQL 16 is only exercised by the dedicated `test-postgres` job.- No default CI job exercises S3/MinIO or Docker socket proxy integration. (Redis is no longer a gap: the- `test` job starts a `redis:7-alpine` service container so the queue-on e2e suite has a broker. That suite- skips itself when no Redis is reachable, so it stays green on a machine without one; under GitHub Actions- it fails instead, so a workflow that loses its Redis service cannot report the suite green.)+ `test` job starts a `redis:7-alpine` service container so the queue-on and throttler-redis e2e suites have a+ broker. Those suites skip themselves when no Redis is reachable, so they stay green on a machine without one;+ under GitHub Actions they fail instead, so a workflow that loses its Redis service cannot report them green.)- Performance testing is not automated.- Dashboard browser/visual UI tests are not currently automated; dashboard pure utility tests run via `npm --prefix dashboard run test:unit`.