Codex HawsLabs .NET Analyzer Tests for Diagnostic Locations
Design focused HawsLabs analyzer or code-fix scenarios with small fixtures and assertions on diagnostics or changed source.
中文Install in Codex
Open the HawsLabs .NET analyzer workspace in Codex with the rule ID, source location and existing test fixtures.
- Review `.agents/skills/hawslabs-write-scenario-tests/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/hawslabs-write-scenario-tests/` in your project and save the reviewed file as `.agents/skills/hawslabs-write-scenario-tests/SKILL.md`.
- Start Codex from that project's root, then type `$hawslabs-write-scenario-tests` and select the matching skill.
Example task
Design an analyzer diagnostic test for this illustrative rule.
{"rule":"HL9001","scenario":"unused local variable","line":4,"column":9,"fixRequested":false}What to check
Use a small analyzer unit-test fixture and assert `HL9001 at 4:9`. Add a comparison case that reads the variable and produces no diagnostic.
Original SKILL.md on GitHub · Updated
Frequently asked question
When should a test assert the exact fixed source?
Assert the expected changed source for a code-fix scenario. An analyzer scenario can focus on the diagnostic.