Mike Harris' Testing and Quality Blog
I have been reading John A. Dues’ new book Win-Win W. Edwards Deming, the System of Profound Knowledge, and the Science of Improving Schools with the Deming Profound Book Club. John Dues uses an equation to describe who is responsible for student performance[1]. This equation works as a useful analogy to describe who is responsible …
Continue reading “Who is responsible for quality? Is it the tester, or the team?”
Testing can be hard, particularly when time is short because the team has a tight schedule. While working with Rob Falla I learned to use Critical Path Analysis to help my team deliver work on time, which helped me have more time for testing. Sometimes it is hard to complete the work that a team …
Continue reading “How to help your team complete their work and so have more time for testing”
On Friday 16 May 1924 Walter Shewhart gave his manager at Bell Telephone Laboratories a memo. The memo “suggested a way of using statistics to improve quality in telephones.[1]” Shewhart’s memo proposed using Statistical Process Control, including Control Charts for visualisation, to improve quality. Shewhart sparked “a revolution in quality control”[2] that can help us …
Continue reading “Gain insights by using control charts to analyse your performance test results”
Sometimes testers are asked how long it will take to automate a batch of tests. Planning how long your test automation should be simple, however, the plan will have missed some requirements. There are three types of requirements[1]: “We will never understand all the requirements of a story ahead of time”[2], this applies to test …
I am using Playwright to automate end-to-end tests, and have started to complement my Playwright tests with Chromatic tests. The Playwright tests are really useful, but each test needs to run through several steps to create a scenario I want to test. Creating a Playwright test for each input variation for each part of the …
Continue reading “Do Chromatic tests complement Playwright tests?”
Testers can help increase cooperation across the company, and cooperation will help us and the company. Testers give feedback to developers when we test. We should also get feedback from other departments and customers on our work and the product we are testing. The feedback we get from cooperating with other departments brings the perspectives …
Continue reading “Cooperation helps to improve testing, helps testers and helps the company”
I am interested in how thinking slowly can help me test and I have been reading Gene Kim and Steven Spear’s new book Wiring the Winning Organization: Liberating Our Collective Greatness Through Slowification, Simplification, and Amplification with the Deming Profound Book Club. Spear and Kim acknowledge how Daniel Kahneman, who recently passed away, influenced them …
Continue reading “Think slowly when you are testing And Think slowly when you are automating”
“Cease dependence on inspection to achieve quality. Eliminate the need for inspection on a mass basis by building quality into the product in the first place.” [1] is one of W. Edwards Deming’s 14 Points for Management. Inspection can be defined as testing after development has been completed. Some people have interpreted Deming’s point as …
When we are automating and maintaining tests we need good feedback on test runs. Playwright gives quick and useful feedback in its Trace Viewer which provides feedback on the run of tests. Trace Viewer’s feedback is one reason I like automating tests with Playwright. Through Trace Viewer you can: If a Playwright test fails, Trace …
Cecelia S. Kilian was W. Edwards Deming‘s long-term secretary. She created this book which contains her memories, and many curated documents from Deming. I read this book with the Profound Deming Book Club and it made me think about why I am interested in Deming. The details of Deming’s life are interesting, however I am …
Continue reading “Get insights from “The World of W. Edwards Deming” by Cecelia S. Kilian”
Whichever technique is used to create tests they will contain assumptions about the nature of bugs. Each technique targets a different set of bugs. If development teams react to bug reports by fixing the bugs that have been reported and by finding and fixing similar bugs, then running the same tests is unlikely to find …
Continue reading “The Pesticide Paradox is a reason to do exploratory testing”
We need psychologically safe workplaces. Testers, and all other members of development teams, need to feel safe enough to be able to ask questions and express opinions about the project we are working on. The need for psychological safety is not a new issue. W. Edwards Deming saw it as an important issue. Drive out …
Continue reading “Drive out fear to improve psychological safety”
To help me test I used to find it useful to think about what quality is for the application that I am testing. “There has been a tendency to conceive of quality as indicating the goodness of an object.”[1] There are many aspects to quality and I have found that this idea of quality is …
Three testers walk into a bar…and we all know that they order, one beer, zero beer and minus one beer! We also all know that they need to order zero beers because the behaviour of zero can be different from the behaviour of other numbers. We all test with zeros for this reason. Recently I …
It can be useful to define aspects of a product that describe the quality of the application that you are testing. I have found examples of doing this in seven different decades. Sometimes these aspects have been put into sets, lists or groups and have sometimes been called quality characteristics, sometimes quality factors and at …
Continue reading “Test using Quality Characteristics\Factors\Attributes that you create.”
TestAndAnalysis