Hiring Good Testers

Abstract: I frequently get asked how I interview testers, be it anyone from exploratory to automation and anywhere within that spectrum (i.e. including “Toolsmiths”, see Richard Bradshaw’s work here for context on that term). What the person is really asking me though is, “How do you know someone who interviews well will actually perform well once

Testing Terminology

Abstract:Another brief post, reacting to a culmination of bad posts I have seen lately in the testing community surrounding the testing terminology we use to define our craft. With language comes power, and this terminology tells others what we think about our craft. Much of what I have seen lately casts testing in a negative

What is Testing?

Abstract: A brief post, the tip of the iceberg on exploring the question ‘What is testing?’. If this intrigues you, then comment or contact me and let’s have a deeper discussion. Updated: April 19th, 2018 (added my mental model to give a visual/be more explicit about my more general statements) Many people confuse “checking” for

A Tester’s Guide To The Galaxy

Abstract: I’ve created a reference card pack that you can use to do better testing, by fostering a team-driven approach to collaborative holistic exposure of high-value product risks. Overview: There are three main ways that we learn: Ingestion (books, blogs, models), Collaboration (conferences, discussions, webinars, meet-ups) and Experimentation (exercises, modeling, day-to-day exploration, etc). Since I recognize there

Testing Manifesto

Abstract: The Testing Manifesto is an encapsulation of a what some of us, context-driven testers, believe the role of “Tester” to be. The skill-craft of testing can be too blurred in many environments, such that we thought this was necessary to put out there. While we’ve used this internally for a while now, we were prompted to share this after

My Testing Journey

Abstract: This is a personal experience story about where I started as a tester and how I have grown through my experiences and interaction with various mentors along the way. I’ve moved from a gatekeeper to an informer, mainly due to the influence of some smart minds along the way that took their time to

A Documentation Story

Abstract: This is a story about an experience that Brian Kurtz​ and I had in shifting test documentation strategies from and all-manual unintentional approach to the utilization of an exploratory logging tool. We also talk about our observations on how that worked overall to our advantage within our context, in recapturing both time and operational

A Personal Metric for Self-Improvement

Article revisions: Learning is continuous, thus my understanding of testing and related knowledge is continually augmented. Below is the revision history of this article, along with the latest version. December 31, 2015, Version 1.0: Initial release. March 31, 2016, Version 1.1: Most definitions reworded, multiple paragraph edits and additions, updated Excel sheet to calculate actual team average. July 28, 2016,

Career Paths For Testers

Abstract: At the company for which I work, testers have two main pathways they can pursue: non-technical and technical. The information presented in this post is written with our context in mind, but other organizations may also share this framework in structuring their testing community.  Overview The career path options available to testers, in every organization of

Don’t Lie On Your Resume, Ever.

Abstract: Don’t lie on your resume. Ever. If we don’t immediately shine light on damaging advice, then we secede our integrity to the misinformed. A question was asked recently in the “SOFTWARE-TESTING” Yahoo group from someone who was seeking advice on how to better construct their CV/resume. A lot of tips starting pouring in from the group, and

Episode VII: The Tester Awakens

Abstract: A brief blog post on being an intentionally awake tester. There’s a lot of misinformation out there, so be a critical thinker and avid learner to properly combat it. It doesn’t take much to live in the dark as a tester. In fact, you simply need to exist. Abide by the rules and listen to

A Sprint Framework For Testers

Abstract: A Sprint Framework For Testers is a brief outline of my suggested processes and practices employed by a Tester that resides within a software development scrum team, in an Agile environment. I have created this document with web-based product software teams in mind, but these practices and recommendations are not necessarily tied to a specific type of software,

Time Trial Testing Episode 2: Risk Heuristics

In this episode of Time Trial Testing, Brian Kurtz and I time-boxed ourselves to a 45-minute session to perform risk assessment of the X-Mind product. We used a heuristic-based risk analysis model to take a look at the UX/UI of this mind-mapping product. See Time Trial Testing – Episode 1: SFDIPOT Model for more details on how

CAST 2015: Distilled

Brian Kurtz and I recently traveled to Grand Rapids, Michigan to attend CAST 2015, a testing conference put on by AST and other members of the Context-Driven Testing (CDT) community. I was rewarded in a myriad of ways such as new ideas, enhanced learning sessions, fresh models, etc, but the most rewarding experience from the conference lies in

Time Trial Testing Episode 1: SFDIPOT Model

Introduction: Recently, Brian Kurtz and I thought it’d be fun to take a look at a process, tool or model within the testing industry at least once per week and use them on a specific feature or product to create a test strategy within a time-box of 30 minutes. Once complete, we draw conclusions letting you