this post was submitted on 05 Dec 2023
54 points (100.0% liked)

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

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
54
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
[–] DmMacniel@feddit.de 6 points 11 months ago* (last edited 11 months ago) (1 children)

who did you ask? Write the UI Tests for your debugged components anyway. Tests are part of development, and if you cant then you write your components wrong.

[–] wccrawford@lemmy.world 5 points 11 months ago (1 children)

I voted you up, but this is tough. I write tests at work when they'll help me, but nobody else maintains or creates them. Except for the tests that the boss created and insists that everyone run.

I haven't pushed terribly hard for my tests, but it's pretty obvious that I wouldn't get any traction if I did, and I'm picking my battles.

So while I agree with "write your tests anyhow", it's a lot harder than it sounds, and a lot less successful than a proper testing strategy that's embraced by the team.

[–] nitefox@sh.itjust.works 3 points 11 months ago

It's pointless if they get mad at me for "wasting time" writing tests and nobody maintains or write them.