57
How do I convince my company to add tests for FE? (sh.itjust.works)
submitted 2 years ago by 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
[–] 5 points 2 years ago (1 child)

Don't. You really can't for most of it. At best, you can test whatever utility functions you have. The FE can and will break more in design than anything else, and that will never get caught by tests.

That said, try a wholistic approach. Playwright requires you to run the back end too, so you get a proper test suite going, instead of jest or whatever.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 2 years ago (2 children)

    Yeah I don't think unit testing would be useful. I don't think though that integration tests etc are useless though, more so now that it is possible to test the UI states too. I didn't know playwright to be fair, I read it "automatically" generates tests? Maybe I did misunderstand

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 years ago

    It doesn't generate them, you still have to write them. Ignore the marketing, look at the actual docs, same as any other framework.

    There's a few other frameworks, I just prefer playwright because I'm used to it.

  • permalink
  • fedilink
  • source
  • parent