Programming

17408 readers

78 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

How do I convince my company to add tests for FE? (sh.itjust.works)

submitted 11 months ago by nitefox@sh.itjust.works to c/programming@programming.dev

25 comments fedilink hide all child comments

We are in a very funny situation where I just spent two weeks fixing FE bugs and there are so many left. I asked to add integration tests but the answer was “no”, cause we can’t test the UI and all of that.

So the proposed solution was to be more careful, except I’m careful but testing whole website parts or the whole website is not feasible. What can I do?

you are viewing a single comment's thread
view the rest of the comments

[–] onlinepersona@programming.dev 8 points 11 months ago

Who's saying this? Other programmers or management?

Programmers might listen to reason, but might be very set in their ways. Some that don't want it might even sabotage it and write crap tests that don't do shit like test that true == true or skip all of them. Know your crowd. If it's a crowd that like copying the latest and greatest, quote something google or facebook did or said. If they're old-school, find some old-ass programmer that loves tests.

Management listen to money unless they're incompetent. Calculate the time it took to resolve certain bugs, estimate the hourly-rate of people, compare that to how much time it takes to write tests, but make it clear that not all bugs can be caught. Maybe even find an article or blog from some manager/CTO/technical lead at another company talking about how bug count dropped or something.

If it's a free for all, add tests yourself.

If they're overbearing, bro, look for another job. A bad culture fit is a bad culture fit and there's no need to fight that. It'll be a learning experience too: not everybody can be convinced and not every company is for you.