13
lotd
2y

Built a whole test suite around our Laravel app which has been pointed out to exec as slowing down CI and yielding no value to the user.

Arguing it’s ensuring something our users is using doesn’t accidentally break just gets brushed off as incompetence.

Oh well, I’ll just skip tests in CI and continue writing and running tests on my own as I don’t feel confident just cowboy fixing things.

Comments
  • 6
    I hate that mindset...
    First they say: "tests are a waste of time!"
    And when you do what they say: "something broke in prod, you should do more testing!"
  • 6
    Show them why it's important. Make some changes that break things, show them that your tests catch those mistakes and prevent regressions. Then ask if they want to deal with angry client when system gets broken, or do they prefer to 'waste' additional 10min for running tests.
Add Comment