[smoll]

In my experience, record & playback tools (like Selenium IDE) generate test code that is a lot more fragile than tests written in code from scratch. I suppose if no one knows how to write anti-fragile tests or it takes way too long, then using a tool like this is a step up. But keep in mind that you may be trading one problem (no one wants to write tests) for another (what the hell are these autogenerated tests even doing? this isn't a regression, it's a feature! etc.)

[chickenfries]

> I suppose if no one knows how to write anti-fragile tests or it takes way too long, then using a tool like this is a step up.

This is kind of the situation I'm in, but I see how you could get yourself in a position where you have no idea what your longer integration tests do because they're generated by Selenium IDE.

Browser integration testing is hard.