zmuxuny opened a new issue, #5028: URL: https://github.com/apache/rocketmq-dashboard/issues/5028
## Problem The `backend-test` job runs the full Maven test suite without a MySQL service. Several `@SpringBootTest` integration tests use the application's default datasource, `jdbc:mysql://localhost:3306/rocketmq`, and need the schema in `server/src/main/resources/db/schema.sql`. On a fresh GitHub Actions runner, they cannot create their Spring context. ## Evidence After the workflow startup issue #4136 was bypassed, [CI run 35838525708](https://github.com/apache/rocketmq-dashboard/actions/runs/35838525708) created and ran all five jobs. The backend test job reported **3,194 tests, 0 assertion failures, 17 errors**. The errors came from nine database-backed test classes (`AuthServiceBootstrapIntegrationTest`, `AuthServiceConcurrencyIntegrationTest`, `AuthServiceSessionOverviewIntegrationTest`, `HealthProbeIntegrationTest`, `NativeAlertEvaluationTransactionTest`, `NotificationOutboxMapperIntegrationTest`, `QueryHistoryServiceIntegrationTest`, `RmqAlertStateMapperIntegrationTest`, and `StudioApplicationTest`). Their context load failures trace to the unavailable default MySQL datasource. On a fresh local `mysql:8.0` container initialized with the repository's schema, all **17 tests in those nine classes passed** without changing application or test code. ## Expected behavior The backend test job starts a MySQL 8.0 service, waits until it accepts TCP connections, initializes the authoritative schema, and then runs `mvn test` against the normal application defaults. Tests explicitly using the `dev` profile should continue to use H2. This is separate from the Docker Action allowlist fix in #4136, the frontend license failure in #5018, and the backend packaging binary license gate. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
