Skip to main content
Microsoft Foundry

Test Case Generator

Description

What this agent manifest does

Point it at a function or spec; get happy-path, edge, and negative test cases enumerated and ready to review.

Build an agent that reads a target function, module, or written spec from a GitHub repository and produces a structured catalog of test cases: the happy paths, the edge cases (boundaries, empty and large inputs), and the negative cases (bad input, error states). For each case it writes the setup, the input, and the expected result in a table you can hand straight to whoever writes the tests — or use as their skeleton.

This is a single-tool read → enumerated test cases pattern using numbered-rule prompt structure. Numbered rules fit because test enumeration is a contract, not a conversation: read the target, classify its behavior, then walk a fixed taxonomy (happy → edge → negative) so the same input yields the same disciplined coverage map. The instructions are explicit that the agent proposes cases for human review and does not assert the set is exhaustive — coverage is the reviewer's call, and any example code is a starting point to run, not a verified test.

This pattern applies anywhere a spec or interface can be turned into checkable cases. Common scenarios for this pattern:

  • Test scaffolding for a new function or endpoint
  • Backfilling regression tests on legacy code
  • Edge-case brainstorming during code review
  • Turning acceptance criteria into test cases
  • Building a QA checklist for a release

The tools it uses

This manifest uses: GitHub

Use this agent manifest to understand

How to build single-shot agents using numbered rules prompt structure for enumerated test cases output.

License

This agent manifest is sample code subject to Azure's licensing terms for Distributable Code under the Universal License Terms for Online Services .

Disclaimer

IMPORTANT! This manifest is for educational and experimentation purposes. Resulting agents are not production ready. Review all provided resources and carefully test agent behavior in the context of your use case. Agents you create may be subject to legal and regulatory requirements, may require licenses, or may not be suitable for all industries, scenarios, or use cases. By using any manifest, you are acknowledging that resulting agents and other output are solely your responsibility, and that you will comply with all applicable laws, regulations, and relevant safety standards, terms of service, and codes of conduct. Learn more .