Red Hat's Hybrid Cloud Console team built a single typed data layer shared across three consumers: the production UI, Storybook mocks, and a CLI tool for seeding and cleaning E2E test environments. By enforcing that all API client imports flow through one data layer (via ESLint rules), any API contract change propagates automatically to all consumers at compile time. The CLI uses the same API clients as the UI, prefixes test resources for isolation, and runs unconditional cleanup to prevent orphaned data. E2E tests are structured as user journeys rather than endpoint checks, covering UI, API contracts, permissions, and business logic in a single pass. The architecture is designed to eventually support operational monitoring using the same test suite.
Table of contents
The problem with separate test infrastructureOne data layer, three consumersThe seeder/cleaner CLIOne investment, multiple returnsWhat's next: From CI signal to operational monitoringWhat I'd tell you if you're building thisLearn moreSort: