• Telorand@reddthat.com
    link
    fedilink
    English
    arrow-up
    29
    ·
    4 months ago

    That should have been caught in QA checks prior to the channel update being pushed out…

    I work in QA, and part of the job is justifying why it’s necessary to keep a team of people that doesn’t actually “produce” anything. Either their QA team is now in the hotseat, or Crowdstrike is now realizing why they need one.

    Either way, it sounds like a basic smoke test would have uncovered the issue, and the fact that nobody found this means nobody bothered to do one of the most basic tests: turn it on and see if it "catches fire.’

    • a1studmuffin@aussie.zone
      link
      fedilink
      English
      arrow-up
      14
      ·
      4 months ago

      God, even if they didn’t have QA test it, they should have had continuous integration running to test all new channel updates against all versions of their program, considering the update will affect all of them. What an epic process failure.