Same thing is happening in academia.
Yes. We're all going to become meat proxies and we're all going to add LLM service uptime as a single point of failure to... every aspect of our technological civilization. But it's all worth it because Grok will let you force feminize Draco Malfoy into a anime girl and that's worth never understanding anything again.
Can you break down for me exactly how the unit and integration tests are made? Do you ask the AI what to assert?
There should be enough detail in the spec that it's pretty obvious. And unlike - many - human devs, agents don't shy away from writing tests. Add a coverage guardrail and tell them to use red/green TDD and you're already a good way there. The main thing is to ensure shared understanding, so they also know business expectations and write appropriate tests. And... nothing here is really specific to an agent, as a human dev also needs sufficient guidance (tailored to their experience level).
Here[0] we have benchmarks for AI writing tests for code that already has the correct behavior. Best case scenario is that they're at 67% with Fable, and that's with the highest quality specification we could possibly have (code). English is far more ambiguous
I have never in my career been afforded the time to make a complete spec.
Noone understood the code to begin with. People understand the concepts, the primitives, the "theory" as Naur said, the basis upon which a project is built. Noone ever understood a codebase worth understanding to begin with.
Noone always gets it right, Noone went there after that horrible incident, Noone actually dances like that...