Use a test matrix to evaluate changes

Write an expected result for each feature

For the adaptive project, test creation, low-health entry, continued damage, repaired exit and re-entry, write observable results such as one entry message rather than a vague pass

场景 / Case | 操作 / Action | 预期 / Expected
出生 / Spawn | 创建战车 / Create tank | 巡航速度 / Cruise speed
低血量 / Low HP | 降到 49% / Reduce to 49% | 进入一次 / Enter once
中间值 / Midrange | 修到 60% / Repair to 60% | 保持应急 / Stay in emergency
恢复 / Recover | 修到 81% / Repair to 81% | 回到巡航 / Return to cruise

Keep comparison conditions fixed

Fix the enemy, distance, unit count and terrain when comparing damage settings, record game and mod versions, change one variable at a time before evaluating the whole design

Scale from one unit to a squad

A behavior that works on one unit may be unsuitable for a large group, try 1, 10 and 50 units, check message spam and responsiveness and reduce unnecessary checks or repeated actions

Record file checks and game tests separately

File checks catch missing art, wrong names and duplicate keys, in-game tests verify behavior, record completed and untested steps and retain the first full error with a minimal reproduction