Comments on: Should you log every bug? http://www.kalyr.co.uk/weblog/computing/testing/should-you-log-every-bug/ The blogs of Tim Hall Fri, 14 Apr 2017 23:35:42 +0000 hourly 1 https://wordpress.org/?v=3.7.41 By: John P. http://www.kalyr.co.uk/weblog/computing/testing/should-you-log-every-bug/comment-page-1/#comment-49938 Wed, 25 Jun 2014 12:17:06 +0000 http://www.kalyr.co.uk/weblog/?p=10834#comment-49938 Now this is what you call a fail!

Just in case the link doesn’t work, the BBC were testing a push alert for their news app that included the text: “Push sucks! Pull blows! Breaking News No nudity in latest episode of Game of Thrones! More breaking news I like testing”

]]> By: @halperinko - Kobi Halperin http://www.kalyr.co.uk/weblog/computing/testing/should-you-log-every-bug/comment-page-1/#comment-49692 Sun, 22 Jun 2014 13:29:24 +0000 http://www.kalyr.co.uk/weblog/?p=10834#comment-49692 Ease the Bug reporting mechanism for such cases, rather then try to find other means to “mention” it to others which will also destruct them but will probably be lost later on.
Minor Bugs can be reported with less “must’ fields, and pass a shorter review cycle
(For instance – straight to PM who will take a decision, and once in a while query for clustering etc. which may have higher overall affects)
If data need to be collected – create a tool to retrieve it in a single-click.
Reduce the effort – not the feedback.

@halperinko – Kobi Halperin

]]>