←back to thread

11 points papapin777 | 3 comments | | HN request time: 0s | source
Show context
chosenman ◴[] No.44523625[source]
So it potentially can outperform/ substitute selenium for frontend testing?
replies(1): >>44523713 #
1. papapin777 ◴[] No.44523713[source]
Basically, it’s built on top of Playwright — kind of like Selenium. The pros are that it’s easy to write tests in English and you don’t need to maintain them. The cons are that you spend tokens, so it costs money for every test run.
replies(1): >>44523831 #
2. chosenman ◴[] No.44523831[source]
So, are you saying that I should spend money on every test run?
replies(1): >>44523902 #
3. papapin777 ◴[] No.44523902[source]
Unfortunately, yes — you need to spend money for every test run. But you’re paying either way. Let me explain: I work at a big company with a large QA team. People write tests in JS/TS/Python. It takes time to write them, and then more time to maintain them when they break due to UI changes. Our team spends a lot of time fixing flaky and broken tests. Time is money. So leadership has to make a decision: should people spend less time writing and maintaining tests and focus more on quality, even if it means paying for test runs?