Mike Harris' Testing and Quality Blog
Creating tests using recognised techniques, such as boundary value analysis, enables teams to create more efficient tests and is a basis for learning about testing. Recognised techniques for creating tests provide a way of analysing functionality that enables the creation of more efficient tests. Teams that use techniques to design tests for their code have …
Continue reading “Using recognised techniques to create tests gives teams advantages”
Each project has different requirements, and each set of requirements makes its own demands on ‘quality’. On every project I work on, I find it useful to interpret ‘quality’ in more than one way. Interpreting quality is more helpful than defining it. A definition is definitive whereas you can have many interpretations. It is useful …
Continue reading “Interpreting ‘quality’ in more than one way helps me uncover issues”
Test analysts, test engineers, test leads and test managers need to understand customers so that our testing includes using the product as the customer uses it. To do this we need to learn how customers use the product by meeting the customer and seeing how they use it. Mr Fuji Cho, the former President of …
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”
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.”
In “Black-Box Testing” Boris Beizer describes a number of useful techniques that can be used for black-box testing. He defines black-box testing as “the testing you do when you put yourself in the software user’s place to verify that it behaves the way it’s supposed to”.[1] Each testing technique is described in a chapter which …
Continue reading “A review of “Black-Box Testing” by Boris Beizer”
There is a discussion in the DORA Community about “the problem with DORA metrics is that they focus on maximizing outputs rather than outcomes”. Some people have argued that Dora metrics will reward teams with a high number of commits, which would be considered ‘output’ but not reward teams whose commits benefit customers, which would …
The Art of Software Testing is a book that I often refer to. The book contains valuable views on how to approach testing and clear descriptions of some test case design methodologies. It was first published in 1979 by Glenford J. Myers and an updated third edition was published in 2012. The book starts with …
Continue reading “A review of “The Art of Software Testing””
Teams whose focus includes testability are more likely to be high performing.[1] Good testability will “minimize testing costs”[2]. Testability can also be seen as one of the factors that determine quality. When the testability of a feature is discussed people often ask what is meant by testability. The clearest definition of testability I have found …
Continue reading “How can you improve the testability of your product?”
I test the steps in the Help documentation for the functionality that I am testing. It is easy to forget to test the examples in Help. Testing the steps used in Help can be useful in more than one way. It is important that the steps described in Help ‘work’ because they are what the …
Continue reading “Don’t forget to test the steps in the Help documentation!”
“The Art of Software Testing” by Glenford J. Myers is a classic book about software testing and I often use it as a reference. In the book, Glenford J. Myers wrote that “test cases that explore boundary conditions have a higher payoff than cases that do not”[1]. Boundary Value Analysis is a widely used testing …
Continue reading “A thought regarding boundary value analysis”
Testers and developers can use the Deming Cycle to improve the quality of their testing. The Deming Cycle was initially used in the manufacture of telephones and has had a big influence on software development. The cycle has four steps: The cycle should be repeated with the knowledge accumulated. The Deming Cycle can be described …
Continue reading “Using plan-do-study-act to improve testing”
Cause-effect diagrams are a useful technique that can be used to improve quality. Glenford J. Myers wrote that “a weakness of boundary value analysis and equivalence partitions is that they do not explore combinations of input circumstances”[1]. A technique that can be used to explore and describe combinations of inputs to an issue is a …
Continue reading “Using Ishikawa diagrams to improve quality”
TestAndAnalysis