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?
Tangential question - what are people using their homelab for / what are some interesting or useful projects you've spun up on them? I've been thinking about setting one up but not 100% sure I'd find use out of it :)
Anyone have good (preferably open source but not required) tools for running MacVMs on a Mac? Would love a way to programmatically control MacVMs (create new from image, start, stop, etc) as part of our Mac build server setup. GitHub actions Mac CI minutes are so expensive so we run our own setup and VM level isolation seems to be the best way to keep the build processes from stepping on each other.
> By the way, I can also help you with more complex math problems, statistical analyses, or even help you learn new mathematical concepts. Do you need assistance with any other math-related inquiries?
Reminds me of my Amazon Echo and the reason I unplugged it :)
Upnext | 100% Remote | Full Time / Contract / Internship | Design / ML
Too many tabs open from HN? Blogs to read in your email, messages and todo apps? Lost that article you wanted to read? Organize it all, follow and find interesting sources of content and supercharge your daily learning with Upnext! We’ve just launched and our building out our team to help us create a next generation reading and learning experience. Check us out at https://getupnext.com!
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?