Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> One feature in beta that we’re really excited about: For React apps we have the ability to target React component names as if they were DOM elements (e.g. if you click on a button you might get a selector like “<NotificationPopupMenu> button”). We think this is the best solution for the auto-genned classes problem described in the bullet above, as selectors containing component names should be very stable.

I remember looking into this exact idea. Theoretically, if you're able to capture the React state, and you're working with a "pure" React app, you should be able to auto-gen readable tests from human interaction. And, if you're capturing the state in a granular enough fashion, you should be able to "time-travel", but for non-technical users.

IMO the biggest use case for E2E tests are for critical things like auth & checkout. If you're able to auto-gen, maybe you can get even deeper than that.

Congrats on the launch, it looks cool!



We have a product that does this (generates E2E tests from user interactions) - it's very tricky. If you just want to cover the auth & checkout flows it's great but if you need to model the more complex and nuanced interactions record + playback is really a great way to go.


You should be able to hack React to do what I'm suggesting (playbacks), though last time I looked at the source code I got a bit confused and gave up.

It's historically been such a battle to deal with E2E tests and changing code, but if this playback idea works well then the interop should be relatively seamless. It might require an over-engineered React app, though, which is likely the biggest issue.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: