I think in this text, details like the timeline are simplified a bit too much. But I agree with the general tendency described.

There was never a time where software was perfect, but the accelerating cadence of serious, widespread incidents with real-world effects seems real.

  • melfie@lemmy.zip
    link
    fedilink
    English
    arrow-up
    8
    ·
    5 hours ago

    I think metrics like code coverage are a big part of the problem where devs are encouraged to stop short of fully testing something or write low-quality tests that prove nothing to satisfy the metric.

    The classic simple example is a divide function that takes a dividend and divisor and returns a quotient. One test that passes 6 and 3 and asserts 2 yields 100% code coverage, but what what about divide by zero errors? Does it work with negative numbers? Etc., etc. You’re definitely not done with tests, despite the metric saying you are, and a slop generator (human or AI) could certainly write a fundamentally broken implementation that passes the tests.

    Now combine that with a tendency to focus on unit tests that test the system in a manner that hardly reflects how it works in production, and you have a system that passes all the tests, yet doesn’t actually work.

    • dandi8@fedia.io
      link
      fedilink
      arrow-up
      6
      ·
      5 hours ago

      This is generally solvable via mutation testing. Sadly, almost no developer knows what mutation testing even is.