How we tested a feature that affected (almost) all parts of GitLab

This post details the challenges and learnings from testing the 'Maintenance Mode' feature, which impacts nearly all parts of GitLab. It highlights the need for crowd-sourced testing by involving engineers from all 13 stages to identify critical features for prioritization. Key learnings include the importance of iterative and collaborative testing, asking other teams for contributions, clear communication, recognizing documentation's role in developer communication, iterating on discussions, and involving more people in the process.