Motivation
Link to the gh-aw PR: github/gh-aw#67439 — "Add declarative JSON schema validation for memory". This adds validation.json-schemas for cache-/repo-/drive-memory, letting workflows declare inline JSON/JSONL schema checks without a custom script. No E2E test exercises this new declarative path (only test-copilot-cache-memory-concurrent-merge.md and a free-form validation.script exist today).
Proposed test
- Workflow file:
test-copilot-cache-memory-json-schema-validation.md
- Trigger:
workflow_dispatch
- Engine: copilot
- Safe output:
create-issue
- Variant: standard
Minimal test prompt sketch
Configure tools.cache-memory.validation.json-schemas with a schema requiring an entries array in index.json. Have the agent write a valid index.json to the cache-memory directory, then create an issue confirming the write succeeded (deterministic positive path — avoids depending on validator failure-issue wording, which is out of scope for this harness).
New fixtures or secrets needed
None.
Notes
Open suggestions #18588 and #20862 cover repo-memory concurrency/sharing, not the new JSON-schema validation feature. test-copilot-cache-memory-concurrent-merge.md does not configure validation.json-schemas. Scope deliberately kept to the success path; a follow-up could add a schema-violation/failure-issue variant once failure-issue wording for memory validation stabilizes.
Generated by 🔍 Suggest New E2E Tests · copilot · auto · 153.8 AIC · ⌖ 5.44 AIC · ⊞ 8.6K · ◷
Motivation
Link to the gh-aw PR: github/gh-aw#67439 — "Add declarative JSON schema validation for memory". This adds
validation.json-schemasfor cache-/repo-/drive-memory, letting workflows declare inline JSON/JSONL schema checks without a custom script. No E2E test exercises this new declarative path (onlytest-copilot-cache-memory-concurrent-merge.mdand a free-formvalidation.scriptexist today).Proposed test
test-copilot-cache-memory-json-schema-validation.mdworkflow_dispatchcreate-issueMinimal test prompt sketch
Configure
tools.cache-memory.validation.json-schemaswith a schema requiring anentriesarray inindex.json. Have the agent write a validindex.jsonto the cache-memory directory, then create an issue confirming the write succeeded (deterministic positive path — avoids depending on validator failure-issue wording, which is out of scope for this harness).New fixtures or secrets needed
None.
Notes
Open suggestions #18588 and #20862 cover repo-memory concurrency/sharing, not the new JSON-schema validation feature.
test-copilot-cache-memory-concurrent-merge.mddoes not configurevalidation.json-schemas. Scope deliberately kept to the success path; a follow-up could add a schema-violation/failure-issue variant once failure-issue wording for memory validation stabilizes.