In a discussion about maintainability of automatic test cases in the area Cucumber + Junit / Unitest the topic "hardening of test cases" came up. You know this topic from your discussions about planning, effort, and how to harden test cases so that you don't have to make constant adjustments.
- I'm especially concerned that we always have changes in the area of API testing, of course, constant changes are a sticking point here.
- So it is both a technical possibility to minimize the process of constant adjustments, but also to adapt the workflow in such a way that changes are included.
- A larger area of the request is probably how I can minimize the effort for expired or changed data, and the changes by the tester? And if I can do this at all?
How can I harden mock based api tests so that they don't have to be changed all the time? (Cucumber + Xray based)
How can I harden functional tests so that they do not have to be changed constantly? (Cucumber + Xray based)
How can I adapt the Definition of Ready / Done so that the area Test Case Adaptation and Hardening is planned accordingly?