Great, but since no human has looked at them, how do you know that they are relevant and actually test undesired behavior?
Also, would you be able to point at which tests should be added in the future?
Great, but since no human has looked at them, how do you know that they are relevant and actually test undesired behavior?
Also, would you be able to point at which tests should be added in the future?
We also use a headless API with a fully decoupled frontend, and the frontend is written entirely by developers. This helps catch additional issues during integration because every endpoint is exercised and validated through the actual userfacing workflows.
I may not be able to convince developers about the process we follow, but we got it working, and tested for concurrency, load and fanout behaviour. This is our primary requirement, as this is targeted towards large scale government customers. Regarding future tests, they will be added for new features, reported bugs, newly discovered failure modes, and regressions. This level of test coverage also helps us use AI without allowing significant drift in the codebase.