Such as counterintuitive fixes to a problem, or where a mistake unexpectedly results in an even better outcome than originally hoped for.

  • LH0ezVT@sh.itjust.works
    link
    fedilink
    arrow-up
    21
    arrow-down
    1
    ·
    8 hours ago

    I found a bug by slacking off.

    Without details, there was a product that we were supposed to test before it hit mass market. It had an annoying bug where it would forget certain configuration items, seemingly at random. Nobody could reproduce it.

    Until me and my friends decided that this was the perfect opportunity to slack off, and took a >1h lunch break (“can’t be online on teams, I’m testing…”). As it turns out, the product goes into deep standby after >30 minutes. Official break time was 30 minutes. So if you take the break on the dot, it will never go to deep standby, and never forget its configuration.

    So, we figured out the bug by taking a long-ass lunch break.

    • Pulptastic@midwest.social
      link
      fedilink
      English
      arrow-up
      6
      ·
      6 hours ago

      Testing should have some specified time windows eh? If the maker knows that the software does a thing at 30 minutes, that should be an intentional part of the test.