• MrScottyTay@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      2
      ·
      6 days ago

      Would be more apt if animals’ physiology was even remotely similar to humans though. Test environments in programming can at least be exact replicas of production environments.

      • usernamesAreTricky@lemmy.ml
        link
        fedilink
        arrow-up
        15
        ·
        6 days ago

        But but it worked on my machine

        In 2004, the FDA estimated that 92 percent of drugs that pass preclinical tests, including “pivotal” animal tests, fail to proceed to the market.More recent analysis suggests that, despite efforts to improve the predictability of animal testing, the failure rate has actually increased and is now closer to 96 percent

        https://pmc.ncbi.nlm.nih.gov/articles/PMC4594046/

        • MrScottyTay@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          6 days ago

          There’s actual medication that was tested on animals that was completely fine then when it got approved it was given to human women and caused crazy amounts of miscarriages. Different species are not comparable when it comes to medication, testing on animals is almost completely pointless.

        • Carighan Maconar@lemmy.world
          link
          fedilink
          arrow-up
          2
          arrow-down
          3
          ·
          6 days ago

          It sometimes feels as if the medical and scientific knowledge of people who are hardline against animal testing at all is exactly that and only that thinking, yes.

  • zqwzzle@lemmy.ca
    link
    fedilink
    English
    arrow-up
    30
    ·
    6 days ago

    Paraphrased: everyone has a production environment, if you’re lucky you have a test environment too.

    • Ajen@sh.itjust.works
      link
      fedilink
      arrow-up
      8
      ·
      6 days ago

      Not entirely true… If you write libraries for other developers you can use them as beta testers. Your customers have a production environment, but you don’t. At least, that’s what one of our vendors seems to think…

    • IMALlama@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      5 days ago

      We have a test environment but it’s a hot mess. All the data is made up and extremely low quality. All the things you would normally interface with are also in test, but getting other teams to coordinate testing in the test space is… a chore. We do the best we can with mock services, but without having real services or representative data some of the data pattern assumptions don’t play out. Leaders value writing code and our lack of architects that span teams mean that when team architects either don’t meet ahead of time, make assumptions, or don’t ever agree on a design then…

      We always host UAT. We also track logins. Guess how many users even show up for UAT, let alone actually click on anything.

      This is why the vast majority of our testing happens in prod when our users are doing real work.

      Sorry for the baby rant :)

  • GissaMittJobb@lemmy.ml
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    5 days ago

    Testing in production rules actually. Use feature flags and monitoring and you’re all good

    • eldavi@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 days ago

      Tags also work well; it’s how I’ve been making hot fixes for that last 3 years. Lol

  • Carighan Maconar@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    6 days ago

    Always test in production!

    Extra environments cost money. Testers cost money. Users pay to use your software and test it for free!