I'm in charge of UAT for our applications and honestly, you fight a losing battle no matter what.
I write a script for each individual aspect of our application, used how it's supposed to be used. Each interaction needs to be screenshotted or something else to prove it was successful. It is the signed off by the tester, who will be a random employee. I require two different testers and have all scripts pass, which at least one full round of testing passing.
If possible, I let other employees play around and try to break the application before it goes out.
I think the mantra is "It'll never be ready, so just ship it". As long as you are confident in the tests and, imo, have proof other people agree with you then it's the best you can do.
I'm in charge of UAT for our applications and honestly, you fight a losing battle no matter what.
I write a script for each individual aspect of our application, used how it's supposed to be used. Each interaction needs to be screenshotted or something else to prove it was successful. It is the signed off by the tester, who will be a random employee. I require two different testers and have all scripts pass, which at least one full round of testing passing.
If possible, I let other employees play around and try to break the application before it goes out.
I think the mantra is "It'll never be ready, so just ship it". As long as you are confident in the tests and, imo, have proof other people agree with you then it's the best you can do.
Checkout cypress.io for that initial acceptance level testing.