<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Testing on Chuanxilu for Skilled Homo sapiens</title><link>https://blog.chuanxilu.net/en/tags/testing/</link><description>Recent content in Testing on Chuanxilu for Skilled Homo sapiens</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 23 Apr 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://blog.chuanxilu.net/en/tags/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Write Test Plans Before Test Code: Requirement Anchoring in AI Development</title><link>https://blog.chuanxilu.net/en/posts/2026/04/test-doc-before-test-code-reverse-anchoring/</link><pubDate>Thu, 23 Apr 2026 10:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/en/posts/2026/04/test-doc-before-test-code-reverse-anchoring/</guid><description>In AI-assisted development, tests are not just verification. They are the most precise requirement language you can give an AI. Drawing from my own failures, this article walks through the full chain from test scenario identification to test development documents, and explains why this method matters far more when the coder is an AI.</description></item></channel></rss>