* WIP npm publish setup
* verbose startup + error if cline core not found
* working npm release
* modifications for linux npm package to work
* remove publish npm workflow for now
* readme & package.json tweaks
* fix old reference to compile-standalone-cli in test workflow
---------
Co-authored-by: Andrei Edell <andrei@nugbase.com>
* Dont use continue-on-error in the GH workflow
Using continue-on-error makes the tests appear as passed even when they failed and this is confusing
* Increase timeout for getOpenTabs test
* Dont run any tests if the build step failed
* Update .github/workflows/test.yml
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* Fix getOpenTabs on tabs
```
Extension host test runner error 1 test failed.
1 failing
1) Hostbridge - Window - getOpenTabs
should return all tabs including deleted files:
Error: EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\vscode-test-O06Qnd'
```
The test is failing because the clean can't delete the temp directory it created, just surround it with try/catch.
* Add debug logs to the openTabsTest
* Increase the timeout on the e2e tests
I see this test timing out, so try increasing the timeout
https://github.com/cline/cline/actions/runs/18209633465/job/51847553463?pr=6628
---------
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* first pass of removing all related code
# Conflicts:
# src/hosts/external/ExternalWebviewProvider.ts
# src/hosts/vscode/VscodeWebviewProvider.ts
* remove more things
* rename all sidebarWebviews to webview
* remove null from getInstance and remove null checks
* remove client id logic and update RPC subscriptions to match this
* add back extension.test.ts without irrelevant webview panel tests
* Refresh CI cache - fix proto compilation
* add comment to try to invalidate CI cache
* add clean script to test.yml for test-platform-integration
* remove clean script didn't work
* finally found the error in the code - linter wasn't highlighting it
* Don't delete unrelated tests in this PR
---------
Co-authored-by: Sarah Fortune <sarah.fortune@gmail.com>
* improving test workflow
* testing pipeline improvement
* testing new run
* adding missing protos
* adding previous cache + restoring dev dep version
* restoring webview package lock
* scripts update
* fixing old flaky test
* fixing old flaky test
* changeset update
* adding test-platform-integration again
* adding quality check for integration platform
* Migrate to Biome for linting/formatting and simplify hooks
- Add biome.jsonc and @biomejs CLI; configure VS Code to use Biome for format/fix and imports
- Replace verbose Husky pre-commit with lint-staged runner
- Remove ESLint setup and custom rule package (no-direct-vscode-api) and its tests
- Update package.json/package-lock and webview-ui package to reflect tooling change
- Add VS Code host typings and grit definitions under src/hosts
Rationale: unify lint/format tooling, speed up pre-commit checks, and reduce maintenance overhead from custom ESLint rules.
* remove eslint dependencies
* preserve eslint rules
* clean up
* update files list
* add docs
* fix build
* clean up
* update VSCode API usage detection in Grit rule
This commit updates the Grit rule for detecting VSCode API usage:
- Narrow down the list of monitored VSCode API methods
- Add more specific diagnostic messages for direct API usage
- Introduce a new check for `workspaceFolders` property
- Exclude `src/extension.ts` from the Grit rule in Biome configuration
The changes aim to improve code abstraction and provide clearer guidance for replacing direct VSCode API calls.
* adds new cacheService rule
* add back pre-commit
* Remove ESLint custom rule and update linting references
Remove custom ESLint rule for VSCode state API enforcement along with its tests, remove ESLint extension recommendation, and update documentation to use generic "linter" terminology instead of ESLint-specific references.
* update vscode.d.ts for IntelliSense
* remove format on save
* clean up default values
* update to 2.1.4
* buf lint
* format
- Replace fixed 100ms timeout with pWaitFor polling mechanism
- Set 2-second timeout with 50ms polling interval
- Test now waits exactly as long as needed for tabs to be created
* test: Fix and re-enable unit tests
Re-enable unit tests in CI workflow that were previously disabled
The cline-api test requires VSCode SDK which cannot be easily mocked in unit tests,
so it has been moved to integration tests where the full VSCode environment is available.
The @google/genai module is ES6-only which causes issues when running integration tests
compiled to CommonJS. A mock implementation has been added and the module resolution
is intercepted in test-setup.js to use the mock instead.
The bedrock unit tests for getModelId() functionality are removed as they were failing
and fixing them is out of scope for this PR.
- Move cline-api.test.ts from exports to test directory as it depends on VSCode SDK
- Add gemini-mock.test.ts to mock @google/genai ES6 module for CommonJS compatibility
- Add module interception in test-setup.js to redirect @google/genai to mock
- Remove failing bedrock unit tests introduced in PR #4209 (out of scope)
* Update src/api/providers/__tests__/bedrock.test.ts
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* Formatting
---------
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
* Add Playwright E2E tests
Adding end-to-end (E2E) testing capabilities using Playwright. It also updates the `@vscode/test-electron` dependency.
The changes include:
- Adding Playwright as a dev dependency.
- Adding `e2e` and `e2e:build` scripts to `package.json` for running E2E tests.
- Adding `@playwright/test` to the list of dependencies.
- Updating `@vscode/test-electron` from `2.4.1` to `2.5.2`.
- Adding `test-results` to `.gitignore` to exclude test result files.
* wip: github workflow
Adding a new GitHub Actions workflow for running end-to-end (E2E) tests using Playwright. The workflow is triggered on push to the main branch, pull requests, and manual workflow dispatch.
The workflow defines a matrix strategy to run tests on different runners (Ubuntu and Windows) and shards. It also uploads Playwright recordings as artifacts if the tests fail.
* add @vscode/vsce as dev dep
* update workflow
* apply feedback
* fix test workflows
* add command palette helper
This commit improves the reliability and efficiency of the end-to-end tests by:
- Adding a delay to the "Let's go!" button click in the auth test to ensure the action is properly registered.
- Adding an expectation to ensure the "Get Started for Free" button is no longer visible after API key submission.
- Caching the "Use your own API key" button to avoid redundant lookups.
- Introducing a `runCommandPalette` helper function to streamline command execution within the VS Code environment.
- Disabling notifications before running the tests to prevent interference.
* state change
* set TEMP_PROFILE
* v3.18.7 Release Notes
* changeset version bump
* Updating CHANGELOG.md format
* Update CHANGELOG.md for version 3.18.7
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: pashpashpash <nik@cline.bot>
* Remove optimistic loading from organization dropdown (#4746)
* update build script to javascript
* fix match
* Add mode switching to chat test
* expected
---------
Co-authored-by: abeatrix <beatrix@cline.bot>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: pashpashpash <nik@cline.bot>
Co-authored-by: canvrno <46584286+canvrno@users.noreply.github.com>
* migrate chatButtonClicked
* changeset
* send targeted event to the controller
* prettier
* add test mock
* continue to fix tests
* fix test mocks once and for all
* fix test mocks once and for all
* try again please lord
* try again
* temporarily disable tests
* revert other test 'fixes'
* one more
---------
Co-authored-by: Elephant Lumps <celestial_vault@Elephants-MacBook-Pro.local>
* add a matrix strategy for testing
* Handle EOL on Windows
* use bash as shell on every os and run the test-ci script
* fix tsconfig path resolution using the __dirnname
* print test results regardless of status
* Limit artifact upload to Linux
* update the test-cli
* Add windows-specific dependencies as optional dependencies
lightningcss-win32-x64-msvc
rollup-win32-x64-msvc
* Do not collect coverage on Windows
* Use UTF-8 on the Python Scripts
* force the ubuntu-latest name to be `test`
* Run pretest in CI to build all tests
* Alias paths when running tests
* Bundle ES modules with esbuild
* alias packages
* Preserve the test scripts exit code and display the output
* Remove outdated test
* Fix: Better Windows path support
* Move to 'chai' for test running
* Fix: Let's start with what we know
* Chore: Add 'root' level file path test, remove less useful tests
* Chore: Add 'root' level file path test, remove less useful tests
---------
Co-authored-by: Dennis Bartlett <bartlett.dc.1@gmail.com>
* add coverage to github workflows
* add changeset
* continue to run on errors
* address comments from ellipsis-dev
* add unit tests, confirm passing
* remove pyproject.toml approach to deps instalL
* use github_output env var
* add verbose mode for debugging
* verbose was not being captured
* std out, not print
* remove 1000 line dump...
* print every line separately to prevent clipping
* build extension before testing
* clean up debugging prints
* break coverage.py into smaller files
* break coverage.py into smaller files
* Relative module names not supported
* rename coverage to coverage_check to avoid naming collision
* rename coverage to coverage_check to avoid naming collision
* debugging missing coverage files
* output error on coverage report
* handling ellipsis-dev comments
* see if we need vscode test deps
* experimenting to try to get it running
* use absolute paths
* put everything in root directory
* address more comments from ellipsis-dev
* import run_command in extraction.py
* fix verbose flag
* use parent parser
* ensure safe command test will allow our commands
* make sure we install before coverage
* update tests to ensure run
---------
Co-authored-by: Dennis Bartlett <bartlett.dc.1@gmail.com>
