Just things like not requiring complex set up steps and wiring up many different services with complicated configurations etc. Keeping things stateless (as much as possible) etc
> Also, do you talking about to stop CI/CD flow? Why not to provide a way to keep that flow on production?
Not sure what you mean, but slow tests can be a major problem. Most of the time these end up being due to no thought going in to not repeating the same setup steps zillions of times. As new tests are constantly added, it makes it harder and harder to keep builds/ci fast.
"How develop/maintain a complex software and at same time keep it simple to set up without a huge bottleneck with Ops team"
If state(ful) is a problem, How about KILL Stateful?
Maybe we need to (re)think about how we are handle with microservices? If true, that's is an good hypothesis to validate in a dev perspective.
Just things like not requiring complex set up steps and wiring up many different services with complicated configurations etc. Keeping things stateless (as much as possible) etc
> Also, do you talking about to stop CI/CD flow? Why not to provide a way to keep that flow on production?
Not sure what you mean, but slow tests can be a major problem. Most of the time these end up being due to no thought going in to not repeating the same setup steps zillions of times. As new tests are constantly added, it makes it harder and harder to keep builds/ci fast.