Skip navigation.

Test analysis

Archeological Black Swans: tales of observation, deduction and lost treasure

general software testing | metaphors | perspectives | test analysis

I had dinner with Michael Bolton and James Bach during STARwest, which was a great feast of ideas and insights in addition to the fine food. One of the interesting new ideas that I hadn’t yet heard of was Black Swan Theory , mentioned by Michael Bolton. As an Australian, I could see nothing unusual about the concept of a Black Swan, but in Europe before the discovery of Australia, a black swan was seen as an impossibility since none had ever been seen. The Black Swan theory relates to an unexpected, radical event that alters your perception of reality. As testers. we are often told the European view that black swans don’t exist (this code is fully tested, two weeks of testing will be more than enough, one retest all you need, works on my machine), but we know that our world is full of black swans we call bugs. There is also the other myth that “all tests must be scripted” disproved by the black swan of exploratory testing.

Testing Lessons From Civil Engineering

context-driven testing | development methodology | events | functional testing | general software testing | heuristics | patterns | perspectives | test analysis

Below is the paper I submitted as a prologue to an experience report, discussion, and (hopefully) additional research that I'm presenting for the first time during:

Attend CAST

Performance Testing Guidance for Web Applications book

performance testing | project management | test analysis | test management

Some time back, I blogged about a book I’d been significantly contributing to being available as a free .pdf download. (see the entry here)

Well, the book quietly appeared in “dead tree format” (as Stuart Moncrieff put it in his blog post about the book) a couple of weeks ago and I’ve been getting light heartedly scolded by some of my friends and readers for not making a big announcement, so here’s my “big announcement.”

Performance Testing Guidance for Web Applications

Performance Testing Guidance for Web Applications

by: J.D. Meier, Scott Barber, Carlos Farre, Prashant Bansode, and Dennis Rea is now available on Amazon.

A Month of Gatherings

events | exploratory testing | general software testing | industry recognition | test analysis | test techniques
I have just finally landed after spending a month running around to various conferences and workshops. I will discuss each of them in a bit of detail below, but first I want to talk about the entire experience.

Conferences, tradeshows, and workshops have many purposes. For vendors, it is an opportunity to try and get your wares in front of an interested audience. For practitioners, it is an opportunity to see the latest in tools and technology, and attend tutorials and sessions, sometimes from prominent industry leaders. And for everyone, it is an opportunity to meet new colleagues, reconnect with old friends, and engage in that most basic and valuable activity of any true conference…conversation.

Tester thinking...

test analysis
Say you were given the following requirements...

- Users shall be able to enter any of nine predefined data objects
- User interface shall consist of nine blocks of three rows and three columns
- Each row, column and/or block shall accept only one member of each data object

What am I describing?

Ever played Soduku?

While indulging my (hopefully temporary) addiction to this brain teasing virus, I spent a few brain cells thinking about testing. I thought about what requirements might look like and led me to wonder *why* requirements so often look like those above. Why not just add a picture of the playing "board" and rules of the game? Wouldn't that be easier?

Tracking Intermittent Bugs

test analysis | test approaches
Recognizing Patterns of Behavior In my last post, the term "patterns" caused strong responses from some readers. When I use the term "pattern," I do not mean a design pattern, or a rule to apply when testing. For my purposes,...

How to Investigate Intermittent Problems

exploratory testing | general software testing | test analysis
The ability and the confidence to investigate an intermittent bug is one of the things that marks an excellent tester. I just realized that I haven't yet written about this.So, here is my first cut at a primer on chasing the unreproducible (so far) problem.

Testing an Application in Layers

test analysis | test automation
There is often debate about test automation versus manual testing. When I think about testing, I look at an application in 3 broad layers: the code (on the machine side), the system (where the finished software lives), and the visible...