• cheddar@programming.dev
    link
    fedilink
    arrow-up
    99
    ·
    edit-2
    3 months ago

    A QA engineer walks into a bar and asks where the bathroom is. The bar bursts into flames. The product owner says that the bar can be shipped anyway.

    • psud@aussie.zone
      link
      fedilink
      arrow-up
      23
      arrow-down
      2
      ·
      3 months ago

      As a PO I’m usually asking QA for some tests that actually show the product meets the requirements

      There might be 50 pages proving it rejects bad input, and nothing showing it can successfully handle a perfectly correct case. We seem bad at training testers.

      • cheddar@programming.dev
        link
        fedilink
        arrow-up
        9
        ·
        edit-2
        3 months ago

        That sounds strange. I cannot comment on your particular case without seeing the test artifacts.

        Generally speaking, there is nothing wrong with tests that ensure bad input doesn’t break the system, as this can easily lead to incorrect system states, damage to the environment, loss of data, money, reputation, and even lives - although most systems are not critical enough to threaten lives.

        You wouldn’t need QAs if you only needed to validate that the product meets the requirements. In a typical company, many people are involved in that process. This includes the developer who wrote the code, the developer who reviewed it, and the people who conduct acceptance testing, among others. If your developers produce code that doesn’t meet the requirements, you’re in trouble.

        I’m not saying that QA shouldn’t validate whether the system meets the requirements, but you don’t want them to do just that.

        • psud@aussie.zone
          link
          fedilink
          arrow-up
          3
          ·
          3 months ago

          If they didn’t properly test validation I would complain about that, what that regularly miss is a test showing correct function for each major use case

          • prettybunnys@sh.itjust.works
            link
            fedilink
            arrow-up
            2
            ·
            3 months ago

            So it sounds like you need to use the words to tell them, do you know testing types and strategies so you can tell them which to employ?

      • fibojoly@sh.itjust.works
        link
        fedilink
        arrow-up
        7
        ·
        3 months ago

        Doesn’t sound too weird to me. In my experience, devs always focus too much on positive / correct inputs, as they want things to work. Which is why you need testers that will catch all the weird crazy ways people can break things. Testers shouldn’t even see the code of it can’t handle nominal cases.

      • toynbee@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        3 months ago

        The problem is that testers are competent, often intelligent individuals. Users, not so much.

  • eestileib@sh.itjust.works
    link
    fedilink
    arrow-up
    66
    ·
    3 months ago

    I still fondly remember the QA guy on the first consumer electronics project I worked on. He didn’t do scripting or test harnesses or dependency injection, he used the product and filed good bugs telling us what would fuck up our customer’s expectations.

    A good QA person helps with product design too if you let them.

    Andy B, I’d work with you again in a second.

    • dactylotheca@suppo.fiOP
      link
      fedilink
      English
      arrow-up
      22
      ·
      edit-2
      3 months ago

      Some plans less so than others.

      Also, I like this framing of users as the enemy. Matches my experience, really.

  • Captain Aggravated@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    3 months ago

    Ninety-nine billion, nine hundred ninety-nine million, nine hundred ninety-nine thousand nine hundred ninety-nine bottles of beer on the wall,

    Ninety-nine billion, nine hundred ninety-nine million, nine hundred ninety-nine thousand nine hundred ninety-nine bottles of beer,

    You take one down, pass it around,

    Ninety-nine billion, nine hundred ninety-nine million, nine hundred ninety-nine thousand nine hundred ninety-eight bottles of beer on the wall.

    • TheOakTree@lemm.ee
      link
      fedilink
      arrow-up
      3
      ·
      3 months ago

      Unfortunately the bar was built on long int so it overflowed 23 times and landed on about 1.2 billion.

      One billion, two-hundred fifteen million, seven-hundred fifty-two thousand, two-hundred-something bottles of beer on the wall, one billion, two-hundred fifteen million, seven-hundred fifty-two thousand, two-hundred-something bottles of beer! Take one down, pass it around…

      One less bottle of beer on the wall :)

      • Captain Aggravated@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        3 months ago

        I wonder what would happen if it was a singed long, and it landed somewhere in the negatives after overflowing multiple times?

        Negative forty-eight thousand, six hundred thirty-three bottles of beer on the wall,

        Negative forty-eight thousand, six hundred thirty-three bottles of beer

        You take one down, pass it around,

        Negative forty-eight thousand, six hundred thirty-four bottles of beer on the wall

        • TheOakTree@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          3 months ago

          Well, silly me, I should have specified that I did my calculation with signed long, though it shouldn’t affect the outcome much given my rounding at the hundreds.

          I like the idea of beer debt to the wall, though!