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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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
There's a VS Code extension that records the steps you took and creates the test for you. But more often than not, you would have to make some changes too.
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.