Skip to content

WIP: Share Linux Runner for VSCode UI Tests#1724

Closed
AndriiFilippov wants to merge 18 commits intorelease/v2.0from
enhance/shared-linux-runner-for-ui-tests
Closed

WIP: Share Linux Runner for VSCode UI Tests#1724
AndriiFilippov wants to merge 18 commits intorelease/v2.0from
enhance/shared-linux-runner-for-ui-tests

Conversation

@AndriiFilippov
Copy link
Collaborator

@AndriiFilippov AndriiFilippov commented Dec 16, 2025

Description

since we won’t be developing new features for the Eclipse IDE, the load on the Linux runner will decrease. Therefore, we could share the same runner for both IDE and VS Extension UI testing purposes.

Fixes (VSC-1812)

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Test Configuration:

  • ESP-IDF Version:
  • OS (Windows,Linux and macOS):

Checklist

  • PR Self Reviewed
  • Applied Code formatting
  • Added Documentation
  • Added Unit Test
  • Verified on all platforms - Windows,Linux and macOS

* draft eim integration

* update init extension auto config

* rm global state idf setups

* do not show invalid extension when showOnboardingOnInit is false

* rm duplicate code

* update welcome show

* fix new projext examples esp idf loading

* update default esp_ide json file

* add eim verify idf setup functions

* update to eim_idf json file name

* save settings as env variables

* rm settings use customExtraVars instead

* fix save docker settings

* check empty customExtraVars PATH

* fix getConfigurationSettings

* rm old setup

* fix lint

* rm setup webpack update python in project test

* use customextravars first

* add selected workspace global config

* use process env if customextra vars not available

* default tools path

* test doctor command

* write customExtraVars from process env if available

* fix workspace arg

* update menuconfig test rm doc cmd

* add PYTHON env var

* log doctor command output clean project first

* add missing timeout

* test debug vscode

* add PYTHON env var

* add env PYTHON save settings

* fallback on global state setups

* escape activation script path if spaces

* move IDF_PATH to workspace state, move frameworks settings to customExtraVars

* update rm global setups

* use env vars if idfSetups not defined, rm redudant code downloadManager and tests

* read esp idf setups from esp_idf.json

* await getConfigurationAccess

* add logger init

* fix IDF_TOOLS_PATH not defined if default

* add PYTHON to env variables

* change checkIdfSetup to isIdfSetupValid rm IEspIdfTool fields

* remove env systemDriver use C in Windows default eim_idf json path

* log activation script output

* change to error logs

* update activationScript split regex

* fix IDF_PYTHON_ENV_PATH to envDict

* loadIdfSetup save idf.gitPath

* add path to prepareEnv

* fix idf size ui

* add idf setups in doctor command

* add validation for eim load env setup

* idfSetupToUse add validation

* fix load idf.currentSetup

* rm idf.espIdfPath from docs rm duplicate idfSetups use old idf.espIdfPath if no idf.currentSetup

* add download extract install run eim from extension

* fx linux exe call

* use env shell for activation script

* allow pick mirror eim download, add l10n for msg

* fix errors

* fix env vars in clang validate

* use latest vscode-extension-tester

* use eimPath field in eim_idf json to open existing executable if exists

* rm idf setup validation, only in doctor cmd

* fix checkPyVenv object

* rm idf.toolsPath reference

* use idf toolsPath old setting to find esp_idf json file

* rm use of ESP_IDF_VERSION in status bar

* add missing v for idf version

* update walkthrough install step

* add idf.eimExecutableArgs for eim gui or cli

* use & intead of launch process

* make sure that eim_unified_release is not cached, rm quote

* close notifications befor doctor cmd

* mv dismiss to before

* fix lint

* fix ts issues

* use default tools path instead of temp for eim download

* add default EIM locations to match Espressif IDE and use EIM_PATH

* test json reporter no use of docker

* add expected test env vars

* add results in console too, rm actions idf fix doctor test

* replace user path in doctor test

* test using e2e ui reports

* test extester mocha options

* update options as object

* update reporter option

* try to parse json from console

* fix console output parsing

* update console output parse error handle

* clean json step

* update test log to test locally

* rm text after closing json

* update end regex

* update parsing with test data

* fail on test error

* update bulma packages and use new syntax
@AndriiFilippov AndriiFilippov self-assigned this Dec 16, 2025
@AndriiFilippov AndriiFilippov changed the title Share Linux Runner for VSCode UI Tests WIP: Share Linux Runner for VSCode UI Tests Dec 16, 2025
ci: testRun

ci: added corepack to enable yarn

ci: set yarn@v1

ci: remove yarn package. add debug step

ci: remove debug
@AndriiFilippov AndriiFilippov force-pushed the enhance/shared-linux-runner-for-ui-tests branch 2 times, most recently from 1706b0c to 6d08015 Compare December 19, 2025 18:05
@AndriiFilippov AndriiFilippov deleted the enhance/shared-linux-runner-for-ui-tests branch December 28, 2025 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants