fix(tests): make ACP model selection resilient - #1444
Conversation
Test Results (Node.js 22)test: Run #116
🎉 All tests passed! |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
3d21f15 to
fe76087
Compare
Test Results (Node.js 22)test: Run #120
🎉 All tests passed! |
|
Good direction. Choosing a model from the ones the session offers is the right fix for the hard-coded 1. The success-path check can't fail. 2. The prompt tests now run on an arbitrary model.
3. 4. The selector ignores models advertised through 5. Nit: duplicated capability check, and a test-only option in production code. Checked locally: the |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
Addressed all five points in three follow-up commits:
Validation: 57 focused tests pass; |
Test Results (Node.js 22)test: Run #122
🎉 All tests passed! |
|
Copilot resolve the merge conflicts in this pull request |
…p-model-resilience # Conflicts: # apps/workers/coder-acp-copilot/src/copilot-cli.integration.test.ts Co-authored-by: duffney <8146181+duffney@users.noreply.github.com>
Resolved the merge conflict and merged current |
Test Results (Node.js 22)test: Run #144
🎉 All tests passed! |
Summary
Closes #1439.
modelsor modelconfigOptionsinstead of hard-coding a server-controlled model IDnewSession, while preserving fixedTEST_MODELoverridesFollow-up commits
14a3e2ac— expose typed model-selection state and consolidate capability detection53f6d643— isolate model selection from the coding prompt and preserveTEST_MODELprecedencecd2c166c— support non-default models advertised through typed ACPconfigOptionsTesting
pnpm exec vitest run apps/workers/coder-acp-copilot/src/acp-client.test.ts packages/test-utils/src/harness.test.ts packages/test-utils/src/run-test-worker.test.ts— 57 tests passedpnpm --filter test-utils build— passedpnpm --filter coder-acp-copilot build— passedGITHUB_TOKEN; the unchanged Docker bootstrap failed before compilation because both Corepack and npm hit aregistry.npmjs.orgTLSECONNRESET, so the authenticated coding/model probes could not run locallyDocumentation and compatibility
No user-facing API, CLI, Portal, database, or deployment behavior changes. Inline integration-harness documentation now covers dynamic probe selection and
TEST_MODELprecedence.