It doesn’t matter, if we’re doing it in once a quarter, or for a two-week sprint – test planning is crucial. But if you start by jumping into specific testing scenarios, I promise you, it’s going to bite you in Read more…
Did you know that September 9th is Tester’s day? Apparently, the first bug was found on 9/9/1947. Note that we’ve been writing programs before that. So if that’s the first time a bug was found, I’d say it’s a bit Read more…
If you’ve been through some kind of an agile transformation you’ve probably heard of the “Definition of done”. Now, let’s talk about that, since we all have a dictionary. I mean, should we define words that we learned when we Read more…
Let’s talk about the testing pyramid. And since it’s a pyramid, I’ll also throw in a tip (see what I did there?) You may have seen the test pyramid with different steps,or levels, in it.It used to be called the Read more…
Data-driven tests are like the early promise of Java: Write once, run many. With some side effects. Just like Java. Here’s a very VERY simple example. This is an API for authentication: Without looking at the code behind it, you Read more…
When we’re testing an application, features, or APIs, we usually think about what they do, the functional stuff. But today, it’s even more important to address how well they do that functional stuff. Enter NFRs: Non-Functional Requirements. Testing NFRs requires Read more…
Today I want to talk about a special kind of tests: Verification tests. What do we want from our tests? Not a lot, really. We just want to know that everything’s ok (when they pass), and when they fail – Read more…
Fragile tests are a scourge on technology. And testing technology. Sometimes they pass, sometimes they fail, and to make life interesting, sometime they just stop, and on the odd case, come up with a very unusual result. “Fragile tests” is Read more…
Why do we test? There are many reasons for testing. But let’s look at it from a business perspective: Why are people paying us? Well, as we know from our own experience, the things we build don’t work as well Read more…
As we all know, because we’ve all gone and read the HTTP specification, when you CREATE a resource, you should get a 201 (Created) response code. It’s an API testing staple. Ok, so not everyone has read it. That’s OK Read more…
