Programming

17398 readers

107 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

23 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

[–] flumph@programming.dev 6 points 11 months ago (3 children)

Just add them. You're a developer and automated testing is one of our tools. A woodworker wouldn't ask permission to sand.

[–] 3h5Hne7t1K@lemmy.world 3 points 11 months ago

This is terrible advice. Communication is the solution.

[–] nitefox@sh.itjust.works 3 points 11 months ago (1 children)

Then I will be scolded for wasting time adding tests

[–] glitches_brew@lemmy.world 3 points 11 months ago* (last edited 11 months ago) (1 children)

Sounds like you need to answer back with numbers.

Calculate how much time is needed for writing tests.

Then calculate how much time was spent writing ineffective code, then add the amount of time it took to rewrite that same code.

I guarantee the latter amount will be more.

Bonus points if you can calculate the amount of money lost from an unavailable application, then add in the amount of money lost from the confidence your customers are losing in that app.

[–] CmdrKeen@lemmy.today 2 points 11 months ago

How do you calculate those numbers though?

It's not like your colleagues will be keeping track of how much time they've wasted writing ineffective code. If anything, they'll try to hide that by arbitrarily inflating sprint points etc.

I've worked in environments like that and the issue almost always isn't that people wouldn't LIKE it if there were tests, it's that they

Don't want to have to learn something new in order to do the same job they're already comfortable with
Are worried that if they convince management to let them invest X amount of time into doing something that will improve productivity, they'll be expected to be more productive in the future

And of course, all of this for no extra money. Unless you work at a place where management prioritzes developer happiness over how many sprint points the team can knock out every week (and those are rare), the sad truth is that it'll likely be about as popular as leftover food growing mold in the community fridge.

[–] killeronthecorner@lemmy.world 0 points 11 months ago

Exactly this. They aren't for the company, they're for you to have confidence that your shipped code isn't going to blow anything up.