Can we learn something for Sherlock on how to debug UI automation problems?
There are commonalities between debugging and a crime scene
Both have a couple of unknowns we have to find answers to
With the exception of a murderer trying to clean his tracks..
But debugging complex code bases can be somewhat similar too, in terms of the unknowns
The first thing to learn is study data that is available instead of jumping directly into reproducing the problem
Most often we don’t have enough data (or understanding) which is a situation we should not have in the first place
By analyzing data we can arrive at a very precise reason why there is a failure
Which, in turn, helps us solve the problem in the first or second debug attempt
If not, then the good old ‘buck shot’ method hoping to luckily stumble over the problem is attempted (we are all very familiar with)
For more lessons from Sherlock:
Leave A Comment