You know I like cool names and puns and memes. And then I choose a name like “Intro To Web Testing” which sounds a bit boring. I should have gone with something like: “Madame Web – Better With Tests”. In the webinar I showed different aspects of web testing. The Read more…
It was my pleasure to present my session “API Exploratory Testing with Postman” on the Continuous Testing Meetup. Good questions, great discussion, and after the meetup I thought – is exploratory testing part of continuous testing? The answer is yes, but you have to work at it. We usually get Read more…
Continuing with API basics, let’s talk about what makes testing APIs, and APIs themselves complex. There are just too many moving parts. The examples are taken with Postman, but the content is tool-agnostic. An API (Really an HTTP request, otherwise we ges even more complex options) consists of 4 parts. Read more…
We haven’t done basics for a while, so let’s start with what an API is and isn’t. It’s important to know what we mean by “testing APIs”. An API is: Application Programming Interface. Fancy words for how to let other computers talk to mine or yours. Or really, any software Read more…
Spring is in the air! Almost. It’s just starting. But it already looks promising. So here are some of the events where you can see me, meet me, greet me, and of course, give me fruit. Or ask me for help. Outside the webinars and virtual events, I’m going to: Read more…
This webinar has started out with a common topic I discuss in my workshops: Test types. People always want to know about what is a unit test vs. component test. But it goes deeper than that. Everybody knows what an API test is, but when you’re testing a whole service, Read more…
Some call them flaky tests. Some call them fragile tests. Or unstable. I say it’s neither, it’s the code. Nobody likes them, regardless. But here’s something interesting I heard in a conversation with one of my clients. He said: “I like calling them flaky tests, not fragile”. Why? I asked. Read more…
I don’t get tired of hearing that question, because if I did, I’d need to sleep for a couple of years. It usually comes up with unit tests, as developers prepare to test their day-old or year-old code. That question has a couple of hidden assumptions that are easily crushed, Read more…
