Abstract: The Agile community has many obsessions, some good, some damaging. One of the most hurtful to stakeholder →
Good testing is hard. It’s a deep intellectual endeavor that requires critical thinking, and among other things, time. →
Abstract: Process frameworks are all the rage; some sold as magic pill, a silver-bullet to solve your organization’s →
Abstract: The job of the influencer or coach/mentor in a software team, regardless of title (Manager, Director, Agile →
Abstract: I frequently get asked how I interview testers, be it anyone from exploratory to automation and anywhere →
Abstract:Another brief post, reacting to a culmination of bad posts I have seen lately in the testing community →
Abstract: A brief post, the tip of the iceberg on exploring the question ‘What is testing?’. If this →
Abstract: I’ve created a reference card pack that you can use to do better testing, by fostering a team-driven →
Abstract: The Testing Manifesto is an encapsulation of a what some of us, context-driven testers, believe the role of “Tester” →
Abstract: This is a personal experience story about where I started as a tester and how I have →
Abstract: This is a story about an experience that Brian Kurtz and I had in shifting test documentation →
Article revisions: Learning is continuous, thus my understanding of testing and related knowledge is continually augmented. Below is the →
Abstract: At the company for which I work, testers have two main pathways they can pursue: non-technical and technical. The →
Abstract: Don’t lie on your resume. Ever. If we don’t immediately shine light on damaging advice, then we secede our →
Abstract: A brief blog post on being an intentionally awake tester. There’s a lot of misinformation out there, so →