Microsoft’s New Testing Agent Tackles the Trust Gap in AI-Generated Code

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

AI coding assistants write code fast. Whether that code can be trusted is a separate question, and it’s becoming a more urgent one. Surveys this year put average developer trust in AI-generated output at just above the midpoint of a five-point scale, and more than half of developers admit they ship AI code without testing it first. Coverage numbers on AI-written code often look fine on paper, but plenty of that coverage turns out to be shallow: tests that check a result isn’t null and call it a day. Microsoft is trying to close that gap with a new open-source agent built specifically for unit testing. Called code-testing-generator, it lives inside the dotnet-test plugin in the dotnet/skills repository, and it’s designed to answer the questions a bare “generate unit tests” prompt leaves open: which code needs coverage, what framework the project already uses, where new tests belong, and whether the build will actually find them. That last point matters more than it sounds. A new test project can compile and pass locally and still never run in CI, because nobody wired it into the solution or the test command. It’s a quiet failure mode, and one Microsoft says its agent checks for directly. How it Works The agent doesn’t jump straight into writing code. It starts by researching the repository: detecting the language, finding the test framework already in use, and studying existing tests to learn local conventions. From there, it scales its approach to the size of the job. A single method gets a direct read-write-validate pass. A larger request triggers planning, and a request …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://devops.com/microsofts-new-testing-agent-tackles-the-trust-gap-in-ai-generated-code/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.