AI: provider CI test coverage

Open
#14,947 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
ai, ci-cd, testing

Research direction

Start with the provider/authentication coverage table and identify one entry marked “needs test,” then locate the corresponding CI test setup for that provider. Add coverage for the selected authentication path and update the table when the CI test passes.

Written by the indexing model from the issue text.

Description

area: assistant

Extracted from https://github.com/posit-dev/positron/pull/14126#issuecomment-4783567479, so we have an easy reference for test coverage across providers. Let's keep this updated as we add CI tests.

- means it's not a supported auth method for the provider, at least at this time.

Provider API key via UI Environment Variable OAuth Credential chain Workbench Managed Auth
Anthropic (anthropic-api) ✅ CI (@:assistant) ⚠️ needs test (ANTHROPIC_API_KEY; CI only sets ANTHROPIC_KEY, which is typed into the UI manually, not the app's own env var fallback) - - -
Posit AI (posit-ai) - - ✅ CI (@:assistant) - -
Amazon Bedrock (amazon-bedrock) - - - ✅ CI (@:assistant) ⚠️ needs test
OpenAI (openai-api) ✅ CI (@:assistant) ⚠️ needs test (OPENAI_API_KEY; CI only sets OPENAI_KEY for manual UI entry) - - -
Microsoft Foundry (ms-foundry) ✅ CI (@:assistant) - - - ✅ CI (@:workbench-azure)
Snowflake Cortex (snowflake-cortex) ⚠️ needs test - - - ⚠️ needs test
Gemini Code Assist (google) ⚠️ needs test ⚠️ needs test (GEMINI_API_KEY, falls back to GOOGLE_API_KEY) - - -
Gemini Enterprise Agent Platform (Google Vertex AI) (google-cloud) - - - ⚠️ needs test -
GitHub Copilot (copilot-auth) - - ⚠️ needs test - -
Custom Provider (openai-compatible) ⚠️ needs test - - - -
DeepSeek (deepseek-api) ⚠️ needs test ⚠️ needs test (DEEPSEEK_API_KEY) - - -
Dominant language
TypeScript
Stars
4.3k
Forks
184
Avg merge
1d 9h
Merged PRs (30d)
195

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from posit-dev/positron

All issues in posit-dev/positron

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.