backend-development

End-to-end integration tests for Encore.ts coordinate subscriptions, polling, and database validation. Import dependencies, execute via the Encore client, poll for async completion with bounded timeouts, assert database state, and clean up—all within a single test flow to verify your backend behaves correctly across layers.

Yes. After triggering async flows through subscriptions and polling for completion, you can assert database state to verify the operation succeeded. This pattern catches integration bugs where async work doesn't persist correctly or leaves the database in an unexpected state.

Use bounded timeout polling: execute your async flow, then repeatedly check for completion up to a timeout limit. This prevents tests from hanging indefinitely while confirming that long-running operations finish within acceptable time windows and actually update your database.

Use diagnostic tooling and integration tests in CI to validate subscriptions, polling flows, and database state automatically. Document findings in playbooks so future changes are checked against the same patterns, catching regressions before they reach production.

Yes. Encore.ts integration tests support importing subscriptions, executing them, polling for results with timeouts, and validating database state changes. This full-stack approach verifies that subscription handlers process correctly and persist data as expected.

Use integration testing when you need to verify subscriptions, async polling, and database state together—not in isolation. Integration tests catch bugs where components work individually but fail when coordinated, which unit tests cannot detect.