Why is "expected" before "actual" in bug templates?



  • I've seen a lot of bug templates all having Expected Result before Actual Result. To me, this does not make sense because it breaks the flow of reading through the bug/page.

    Usually when you read (anything, not just a bug) you'd go:

    top > bottom

    and not

    top > middle > bottom > middle again > almost bottom

    I asked several coworkers why they write bugs in that way the general answer I got was that "that's how it was in a bug template" / "that how I was told to write it"

    Can someone explain why those are reversed in bug templates and what are the benefits of having the expected before the actual?



  • The way I see it putting "Expected" before "Actual" eliminates bias.

    Usually your brain "sticks" to the first things it hears about (that's what Anchoring is about, for example when bargaining the first side to bid will be closer to the final bid) so if you start with the Actual it will be more difficult to see the discrepancies between it and the Expected.

    I don't understand why do you need to read bottom up, at the end of the text you are supposed to remember the two items anyway


Log in to reply
 

Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2