Explore E2E testing across Gitlab / CDot / Marketo
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Currently, our testing strategy across GitLab, CDot, and Marketo lacks comprehensive end-to-end coverage. We primarily rely on manual testing for full integration flows. This approach creates significant risk for regressions and bugs when creating new features or updating API's.
As the Growth team begins contributing to CDot to enable trial experiences through API's, we need to establish integration confidence to catch issues proatively instead of reactionary. This is especially important for critical user purchasing flows.
E2E will:
- verify actual API contracts (request / response works between real service instances)
- expose breaking changes in downstream consumers
- catch timing / timeout issues, retry / logic failures
- validate error handling across service boundaries
Explore and evaluate E2E testing implementations suitable for our multi-service architecture. The goal is to identify a solution that can automate integration testing across GitLab, CDot, and Marketo to reduce manual testing burden and catch integration issues earlier (shift testing left).