• shameless
    link
    1501 month ago

    Was this taken from the Crowdstrike repo?

      • @[email protected]
        link
        fedilink
        191 month ago

        Yeah, but I think apparently the tests that “could” have caught it relied on mocks which basically rendered it useless in those cases.

        • @teejay
          link
          English
          121 month ago

          Ah yes. The unintended consequences of mandated code coverage without reviewing the tests. If you can mock the shit out of the test conditions to always give you exactly the answer you want, what’s the point of the test?

          It’s like being allowed to write your own final exam, and all you need to pass the exam is 90% correct on the questions you wrote for yourself.

        • @marlowe221
          link
          English
          31 month ago

          And this is why mocks are bad…

  • SuperFola
    link
    fedilink
    English
    771 month ago

    Who needs tests when you have users?

    The testing environment is production!

    • @KillerTofu
      link
      61 month ago

      I work in state government and we insist on building our own systems. This is too fucking true and why it’s funny.

        • @KillerTofu
          link
          31 month ago

          We build systems to manage day care licenses in the state instead of buying someone else’s product.

    • @[email protected]
      link
      fedilink
      31 month ago

      Technically there’s no substitute for testing in production lol

      Although ideally you’d want to test it beforehand…

      • @_stranger_
        link
        31 month ago

        There are so many more, and better!, options than testing in prod, but they take time, money, and talent and ain’t no company got time for that (for a business segment that “doesn’t generate revenue”)

      • SuperFola
        link
        fedilink
        English
        11 month ago

        Probably too long. That was a philosophy I had at school and iirc the founders never finished school and started MS in a garage.

      • @residentmarchant
        link
        English
        91 month ago

        Are you like building a mobile app or have 100k tests or is it just super slow?

        • @[email protected]
          link
          fedilink
          121 month ago

          Still waiting on approval for more resources. It’s not a priority in the company.

          I swear we have like 4 runners on a raspberry pi.

        • @thebestaquaman
          link
          21 month ago

          My test suite takes quite a bit of time, not because the code base is huge, but because it consists of a variety of mathematical models that should work under a range of conditions.

          This makes it very quick to write a test that’s basically “check that every pair of models gives the same output for the same conditions” or “check that re-ordering the inputs in a certain way does not change the output”.

          If you have 10 models, with three inputs that can be ordered 6 ways, you now suddenly have 60 tests that take maybe 2-3 sec each.

          Scaling up: It becomes very easy to write automated testing for a lot of stuff, so even if each individual test is relatively quick, they suddenly take 10-15 min to run total.

          The test suite now is ≈2000 unit/integration tests, and I have experienced uncovering an obscure bug because a single one of them failed.

    • @[email protected]
      link
      fedilink
      81 month ago

      I used to have to use a CI pipeline at work that had over 40 jobs and 8 stages for checking some sql syntax and formatting and also a custom python ETL library that utilized pandas and constantly got OOM errors.

      They didn’t write any unit tests because “we can just do that in the CI pipeline” and if you didn’t constantly pull breaking changes into your branch you would guarantee the pipeline would fail, but if you were lucky you only had to restart 30% of your jobs.

      It was the most awful thing and killed developer productivity to the point people were leaving the team because it sucks to spend 40% of your time waiting for CI scripts to fail while you are being yelled at to deliver faster.

  • @Aceticon
    link
    40
    edit-2
    1 month ago

    Who needs integration testing when we have users who will do it for us?!

  • Blackout
    link
    fedilink
    261 month ago

    Lol. I run an open-saas ecom and everything is done live. No one but me handling it. The customers must think they are tripping sometimes. Updates are rarely perfect the first push.

  • @ikidd
    link
    English
    181 month ago

    “YOLO” - more than 1 merge comment I’ve seen.

  • @TootSweet
    link
    English
    121 month ago

    Mo’ unit tests, mo’ problems.

  • JaggedRobotPubes
    link
    English
    81 month ago

    I don’t actually know enough to know anything about this but I’m assuming that’s badass and you can only do it with sunglasses on

  • @AdamEatsAss
    link
    51 month ago

    If QA cared about us they wouldn’t make it so hard.

  • @[email protected]
    link
    fedilink
    51 month ago

    I’m about to do this to this kernel driver. Certainly broken before, possibly broken after, what’s the worst that could happen