The kind of application we test is probably more complex than most as we're a product company supporting a huge number of integrations and specifications. You'

The kind of application we test is probably more complex than most as we're a product company supporting a huge number of integrations and specifications. You're dismissing my claim by basically saying I am naive. Which is not an honest argument as you know absolutely nothing about me (and I don't want to tell you more than I did here). About changing requirements: what does that have to do with testing at all? If requirements change, you basically discard the tests for the old behaviour and start over... I would say that the testing we do is very close to formal verification because it's close to being comprehensive - though no, we do not use methods normally classified as such. I tried to but the benefit we would get over our current approach would be negligible. By the way, I do a lot of UI testing, and dare I say it: yes, it's easy too. We use this sort of thing if you're curious: https://gebish.org/manual/current/#pages https://gebish.org/manual/current/#pages Again, if you find a real example of something you find hard to test, let me know so I can evaluate it against my own situation.