We work in a Safe-Scrum environment with a large number of different teams, and here also correspondingly different test teams.
We have different test cases from different teams, which are combined in our team. These include manual test cases, but also automated test cases.
From these test cases, we should now define various smaller test runs for the individual teams.
But also a complete regression test run that covers all teams.
- Many different teams in the Safe-Scrum environment
- Our team runs all tests together
- Both automated test cases and manual ones
- The test cases are available both in the API area and as functional GUI tests. They are also automated in different Jenkins pipelines (for different teams). So we have more than 30 different pipelines, and this topic is accordingly extensive.
- We have more than 50 teams (no joke) working on different topics for a major customer.
- We developed most of the APIs test as Cucumber based test in a Java/Maven framework with direct integration to Jenkins pipelines and integration to X-Ray.
The problems I see:
We have a multitude of test cases within X-Ray that could not be more different. So there is the danger that you have automated test cases on one side and manual test cases on the other side, which leads to a complex and opaque situation.
There is a risk that we might constantly get new and old test cases that contain manual tests and automated ones and that we constantly have to work on hardening and making adjustments in the team.
How would you deal with this scenario?