3 ms·

Hey, that's exactly what we're trying to make! I think there is a sweet spot for building a better IDE for automation...

• swsieber 9y ago
  We're making a push for more e2e tests where I work. And we very much have a focus on reducing the friction surrounding these tests. We've settled on aiming to build a tool that keeps an index of selectors used <=> page/page structure. Then if something changes, you only have to update it once. So when you create a selector, it'll save it for that page, you can name it and reuse it. Given that we have the source templates too, I think we'll try to validate that the selector will be valid. We might be able to even add tasks for the front end guys that alerts them if the changes they're checking in will break selectors. Combine that will an idea for suggesting selectors based off the source, along with e2e script managent, it'd be a pretty slick tool. It's a pretty ambitious project though. We do hope to make it general enough to open source though. We'll see if we make it (pun intended).