No one among my teammates are testing their code.

We are testing in prod, ok?

@ess3sq Go a step further man, make the customers test it for you.

Be the change, test it for them

The only way to change their behavior, is to be a better example. Always write Tests for yourself, they will keep away trouble and pain from you. And maybe some day also for one of your team mates. Then they will understand. Maybe.

Hesitate, and you lose.

@ostream I don't doubt, I *know* my code is wrong.

Pair program with some and find yourself a testing ally.

Conferences, book clubs, training days, etc are fab ways to demystify tests and get people excited about them

I haven't written a test in two years and I'm happier for it

Github copilot creates tests for you. Don't do that bich work.

Make sure you have tooling to make testing easy as possible.

If you got an API. Make sure all endpoints are in a team postman.

If you have to review code. Maybe write some tests. And see if they'll pass. It's a lot of work but hopefully they'll see where they go wrong, and start to write some tests.

It's hard to get a good testing culture going. So make it as low effort as possible. Try to convince them to write just one test with an input. Once they get used to it. Expand from there.

UI testing is harder to enforce generally.

I know how you feel though. I've tried to get some automated testing going a few times. As that I find the most pallatable way to get them to start thinking about testing differently.

@Shardj I mean. You can get away with it if you test your code really well.

Problem is. Most don't. I also don't think you have to test everything. But like core business functions should have tests.

I don't want to get that 4 am call because someone fucked up the billing service.