Testing and Fault Localization One of the goals of software testing is to produce evidence that a piece of software works as intended. That evidence might be in the form of hard, deterministic data or even stochastic results that statistically show the correctness of the software system to some degree, among others. However, with modern software […]
In this last installment of reachability graphs, I show yet another example of how bugs can be successfully documented (and easily recreated) by reachability graphs. Review the reachability graph below and try it out.
This reachability graph nicely reports an infinite amount of bugs found when using the Google Chrome PDF viewer to search PDFs containing LaTex environments. Try it out!
It’s time for another reachability graph that shows how easy bug reporting can be with them! Follow the graph below and let me know what you find. Enjoy!
Continuing with our exploration of reachability graphs, the graph below shows another very interesting bug in Chrome’s PDF viewer. The beauty of reachability graphs is that it is remarkably easy to follow the abstract states to recreate bugs, and it is impossible to make mistakes in doing so. Go ahead and follow the abstract states […]
Here is another reachability graph efficiently acting as bug report to document a resource-utilization fault found in certain versions of Google Chrome. Reachability graphs are great at documenting any kind of fault, including non-functional defects such as the one for excessive memory consumption below.
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 […]