Continuing the discussion about reachability graphs, here is another reachability graph efficiently acting as bug report to document a bug found in certain versions of Google Chrome. Even if you have an updated version of Chrome, go ahead and try it out for yourself — chances are the bug is not yet fixed and can […]
In the previous post, I showed you how useful reachability graphs can be in documenting almost infinite steps to recreate a bug. Reachability graphs are really the next step in bug reports, where you not only specify how you exposed a specific bug, step-by-step, but it documents how to recreate the bug in a very […]
A fairly long time ago, I introduced reachability graphs and showed you how to start using them to debug applications. After all, debugging is a form of testing. In this post, I’ll continue exploring reachability graphs for the purposes of exploratory testing. To illustrate their useful power, I will use reachability graphs to test some aspects of an […]
You can’t test everything. So how do you know when you can ignore certain events or states from the SUT during structured exploratory testing? Watch the free screencast here:
Reachability graphs help you structure your testing in a way that makes it faster, more focused and helps you avoid dead-ends. Via certain testing patterns that reachability graphs can make visible, it can also help you break through hard-to-test applications and problems. It can even help you debug! Wanna know more? Watch the free screencast […]
Any good software engineer (that includes you, stellar tester!) has heard about development design patterns. However, patterns also naturally occur in the craft and practice of testing.