* 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>
