[jamifsud]

I've been using Claude Code for weeks now and I've found it to be fantastic at writing / debugging tests unit / integ tests that don't require external context. Still needs some guidance of course but it's been a huge productivity improvement.

Unfortunately, I can't say the same for other types of tests like E2E tests. It makes sense why: CC doesn't have access to all of the context to determine what's going wrong. During an E2E test suite run it can't pause to look into the console, view whats on the page, look at the backend logs, etc. I tried writing some utilities to snapshot and log the state of parts of the page when a test failed and this did help a bit, but not enough to get the same productivity boost for other types of tests.

Has anyone had any luck with this? Any strategies to share?