• Alien Nathan Edward@lemm.ee
    link
    fedilink
    arrow-up
    16
    ·
    1 year ago

    This. You don’t know what’s sitting on a jira somewhere with “won’t fix” tagged to it. As an ex-QA who’s now a dev, we want to fix everything and we get told what we will and will not be fixing. When you see bugs in the final product that are relatively easy to reproduce, the story there is almost certainly that we found it and then the money told us not to bother with it because they think you’ll buy the product anyway.

    • _stranger_@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      1 year ago

      My favorite interaction ever, as a QA:

      me: Our integration testing environment is constantly broken due to bad practices among all the teams that share it. They need to be aware of the contract they expose and how they’re changing it before they deploy their code to any shared space.

      management: Given the recent complaints about the instability of the QA environment, we’ve decided to shut it down and eliminate all QA positions.

      • Alien Nathan Edward@lemm.ee
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago

        Our managers did that shit, too, back when I was in the durable medical equipment industry. They said some shit like “QA as an org is dysfunctional, as evidence by all the complaints. We’re gonna streamline the process by eliminating them and having dev teams do their own QA according to this checklist we’ve developed. We think that we can get the same quality for less money and less bureaucratic overhead communicating between the dev teams and the QA team.” They cut about $2 million in annual salary right then and there. A lot of our QA engineers and even a couple of their managers found out about the restructuring at the all-hands where they announced this.

        Fast forward a year, they’re getting the shit sued out of them and have to do a multi-billion dollar recall because of…let’s just call it an “emergent use case” among our customers that no one foresaw and therefore no one tested. That emergent use case was sending people to the hospital. I’ll go to my grave confident that someone whose only job was QA would have absolutely been able to catch that.

        • Alien Nathan Edward@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Lol some of their devices absolutely shipped w privesc bugs, including at least one that could be rooted and I know cuz I was on the team that pentested it but I’m not tryna feed Lemmy some shit that a basic security scan could tell y’all. All I’m gonna say is that if it has wifi or Bluetooth throw scans at it.