TestinGil - Agile SW Testing Consultancy

When you give someone your keys to the house, that means you trust them.

But this is not a specific trust. Do you trust them to not throw parties in the middle of the night?

Or maybe you trust them to do just that?

It doesn't matter, because they got your keys. They'll decide what to do next.

Authentication vs authorization and what they mean to testing.
Watch this:
https://youtu.be/f1Zh_18GTJc

Authentication vs Authorization in API Testing: What Tokens Can't Catch Authentication gets you through the door. Authorization decides wha...

Back in the day, we used to have a rule.
If you're fixing a bug, there's no way it comes out without a test or two. The whole point of regression testing is not have regression.

So do that. And if you want you're genie to help, use this prompt:

"Here's a bug report:

[paste bug description].

Write a regression test case that catches exactly this scenario if it comes back. Include: the setup state, the exact steps to reproduce, and the assertion that would fail if the bug returns. One test, focused on this bug only."

Don't leave bug fixes untested!

We are testing to learn. Once we learn, we believe we can make better decisions. I know I've said it something like 75,639 times.

And it's not easy, because applications are complex. Everything depends on everything else. You push this button, and something you didn't expect pops up. You call an API and you're neighbor gets an unexpected email.

That's why when we look at an isolated APIs, they seem a lot more simple. And simple to test.

Alas, it is only complexity in disguise.

So, when we test, or write tests, or generate them, we still want that learning, and as much as we can of it. Because the goal is the same.

How, you ask? I'll show you.
Webinar tomorrow - Jul-15, 3pm CET / 9am EDT
Register now:
https://us02web.zoom.us/webinar/register/8517677800361/WN_KIU_7yUpRr2yZ8wId1tgSg