Quote:
Originally Posted by thp1017
... I guess for me, the moral of the story is to include as much information as possible when you send a bug report to kobo ...
|
Exactly. Testing is quite an art form and it's essential that the tester is able to tell the developer the exact steps they used before they encountered the error, even if they think they are totally unrelated. Those double page taps you're seeing may have something to do with the fact you were using the browser 5 minutes earlier, but unless you tell the developer everything you've done leading up to the problem he can't follow the trail.
And the description of the error is important too. Simply saying "Can't open book" isn't very helpful. The developer wants to know exactly what happens when you try to open the book; does it come up with an error message and if so what is it, does the book open and then close straight away, does the power light flash to indicate that the reader is doing something but then nothing happens? All of these may give the developer the clue he needs to track down the bug.
In the time that I've spent supporting my own software I've lost count of the number of times I get a bug report that simply says "It doesn't work". Not very helpful at all!