[dead]
Ask HN: How do you go from writing code to deploying with agents?
11–17 of 17 posts
Re: Ask HN: How do you go from writing code to deploying with agents?
#12[dead]
Re: Ask HN: How do you go from writing code to deploying with agents?
#13Testing is not a formality. In fact, it's better and easier than ever. Tell your agents to develop your code-base with Red-Green-Refactor Test-driven development. Write failing tests first and run them, then write the code to make the tests pass, then refactor the code as needed. I used to hate writing tests before, but now that I can offload that (and the development, honestly) to AI, it's nothing to keep up with it…
Yeah, that only works if they follow the plan (they don't), actually write the tests first (they don't) and don't silently defer anything which doesn't have a test written as "speculative without a use case". Or just write tests to match the buggy code after you call them out for not writing tests. I mean, the struggle is real... No matter how weasel-proof you make the plans they are much better weasels and just do a…
You write skills, prompts, and hooks to make them obey. They will obey.
Re: Ask HN: How do you go from writing code to deploying with agents?
#14I'm building solo and am extensionally using Claude Code for development and testing. The following scheme finally works great for me. First of all, the agent writes code. After that, it creates tests and verifies that all of them work correctly by cracking the checks and rerunning the test suite. Secondly, it gives me the ready to test code + set up environment (stage). I'm checking that the code actually works, and…
do you read the code and test code? how do you know that the tests are any good? in my experience a lot of the time it will just mock the expected outcome and then it passes but it doesn't actually test behaviour.
Re: Ask HN: How do you go from writing code to deploying with agents?
#15I'm building solo and am extensionally using Claude Code for development and testing. The following scheme finally works great for me. First of all, the agent writes code. After that, it creates tests and verifies that all of them work correctly by cracking the checks and rerunning the test suite. Secondly, it gives me the ready to test code + set up environment (stage). I'm checking that the code actually works, and…
do you read the code and test code? how do you know that the tests are any good? in my experience a lot of the time it will just mock the expected outcome and then it passes but it doesn't actually test behaviour.
I use a combination of automated and manual testing. I spent a bunch of time setting up playwright testing at the start of my project, and then I shunt that through ZAP as well so that it can have a good understanding of how things work.
If gives me a pretty solid map of what is working well, and aids in driving through security testing.
Still not a replacement for manual testing. Us meatbags still have a knack for royally messing up the expected use cases :P
Re: Ask HN: How do you go from writing code to deploying with agents?
#16[dead]
Re: Ask HN: How do you go from writing code to deploying with agents?
#17Earlier quoted context omitted.
do you read the code and test code? how do you know that the tests are any good? in my experience a lot of the time it will just mock the expected outcome and then it passes but it doesn't actually test behaviour.
I use a combination of automated and manual testing. I spent a bunch of time setting up playwright testing at the start of my project, and then I shunt that through ZAP as well so that it can have a good understanding of how things work. If gives me a pretty solid map of what is working well, and aids in driving through security testing. Still not a replacement for manual testing. Us meatbags still have a knack for r…
Sadly I can't rely on manual testing in my professional work although for personal projects it's how I do it too