Category Label: ~"system testing" | [Issue List](https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=system%20testing&sort=milestone) | [Overall Vision](https://about.gitlab.com/direction/verify) | [UX Research](https://gitlab.com/groups/gitlab-org/-/epics/592) ## Description Modern software is often delivered as a collection of (micro)services to multiple clouds, rather than a single monolith to your own data center. Validating complex interactions to ensure the reliability of the system as a whole is more important than ever. ## What's Next & Why Next up will be a proof of concept of using Docker Compose to run integration tests for a project or group of projects that consists of interdependent microservices as part of https://gitlab.com/gitlab-org/gitlab-ce/issues/22559. From there, we will work with our ~"internal customer" to understand what, if any problems that solves with our current use of [`gitlab-qa`](https://gitlab.com/gitlab-org/gitlab-qa/blob/master/docs/what_tests_can_be_run.md#orchestrated-tests) ## Competitive Landscape ### Azure DevOps TBD ### CircleCI TBD ## Analyst Landscape We do not engage with analysts for system testing market analysis. ## Top Customer Success/Sales Issue(s) There are no top CS/Sales issues for this category. ## Top Customer Issue(s) There are no top customer issues for this category. ## Top Internal Customer Issue(s) TBD ## Top Vision Item(s) TBD