Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Join
4
Likes
8
Comments
Do you use test automation? Why, why not?
by
darou
I worked a lot with Selenium and I don't like it. I work on an alternative as a SaaS service.
Cypress is brilliant. Much more modern and dev friendly.
+1 Cypress, when needed. I’ve use a bit of Selenium over the years, Cypress’ DX is far better.
I’ve heard of it having challenges at scale (when dealing with multiple micro services for example), but AFAIK it’s great for small to medium-sized projects at the. Wry least.
Bugs and performance issues cost software owners reputations, users, and profits. Therefore, to test or not to test is not a question at all. Rather "how to choose the right approach to testing" In general, there are two options automated vs manual testing, each of them has pros and cons, but it should be based on your needs https://www.cleveroad.com/blog/manual-vs-automation-testing/
+1 for Cypress. Not for unit tests, but for a handful of happy-path E2E tests.
I use Cypress.io since they launched, the developer experience is amazing with great documentation 👍
As an app developer, I’m taking the time to setup UI testing. Ultimately it takes longer and longer to manually test and sometimes I miss things. So yes, UI testing is important for me! :)
As a solo dev i feel unit testing and manual is sufficient
Always do testing,