3 ms·
As I dont do frontend work, how do you "test" anything without an insane amount of browsers/hardware realistically ? If I was to write tests, it'd be basically
by worthless-trash 2y ago
As I dont do frontend work, how do you "test" anything without an insane amount of browsers/hardware realistically ?
If I was to write tests, it'd be basically http get/post/put/delete requests and measuring the responses are what I expect.. how can HTMX be any different here ?
How do you "test" a button works without a browser engine ? Every browser engine ?
- creshal 2y agoYou throw headless browsers into your CI/CD pipeline and try not to think about how many resources you're burning.
- homebrewer 2y agoWe do have pseudo-browsers written in pure js that you can theoretically use: https://github.com/jsdom/jsdom https://github.com/jsdom/jsdom https://github.com/capricorn86/happy-dom https://github.com/capricorn86/happy-dom but they're about as reliable as you can expect: it's difficult to keep up the pace with the big three (or two) on standards compliance, and they usually don't even try. So the only reliable solution is a headless Chromium, Firefox, and/or WebKit-based noname browser like the sibling says. https://pptr.dev/guides/what-is-puppeteer https://pptr.dev/guides/what-is-puppeteer https://playwright.dev/ https://playwright.dev/ https://www.selenium.dev/documentation/ https://www.selenium.dev/documentation/