Files
awesome-copilot/skills/acquire-codebase-knowledge/assets/templates/TESTING.md
Satya K b8f3822748 Adds a new Agent Skill - Acquire-Codebase-Knowledge (#1373)
* feat(skill): add acquire-codebase-knowledge skill documentation

* feat(templates): add architecture, concerns, conventions, integrations, stack, structure, and testing documentation templates

* feat(references): add inquiry checkpoints and stack detection documentation

* feat(scan): add script to collect project discovery information for acquire-codebase-knowledge skill

* feat(skills): add acquire-codebase-knowledge skill for codebase mapping and documentation

* feat(scan): enhance scan script with absolute path handling and improved output variable validation

* feat(scan): replace bash script with Python script for project discovery information collection

* feat(skills): update acquire-codebase-knowledge skill to replace scan.sh with scan.py
2026-04-14 10:29:57 +10:00

1.3 KiB

Testing Patterns

Core Sections (Required)

1) Test Stack and Commands

  • Primary test framework: [NAME + VERSION]
  • Assertion/mocking tools: [TOOLS]
  • Commands:
[run all tests]
[run unit tests]
[run integration/e2e tests]
[run coverage]

2) Test Layout

  • Test file placement pattern: [co-located/tests folder/etc]
  • Naming convention: [pattern]
  • Setup files and where they run: [paths]

3) Test Scope Matrix

Scope Covered? Typical target Notes
Unit [yes/no] [modules/services] [notes]
Integration [yes/no] [API/data boundaries] [notes]
E2E [yes/no] [user flows] [notes]

4) Mocking and Isolation Strategy

  • Main mocking approach: [module/class/network]
  • Isolation guarantees: [what is reset and when]
  • Common failure mode in tests: [short note]

5) Coverage and Quality Signals

  • Coverage tool + threshold: [value or TODO]
  • Current reported coverage: [value or TODO]
  • Known gaps/flaky areas: [list]

6) Evidence

  • [path/to/test-config]
  • [path/to/representative-test-file]
  • [path/to/ci-or-coverage-config]

Extended Sections (Optional)

Add only when needed:

  • Framework-specific suite patterns
  • Detailed mock recipes per dependency type
  • Historical flaky test catalog
  • Test performance bottlenecks and optimization ideas