taler-typescript-core

Wallet core logic and WebUIs for various components
Log | Files | Refs | Submodules | README | LICENSE

commit d83315f0c1bdaf2048921dea936151a5330b7115
parent 54c477894d2222d7a2ec549f2843b16517c0a651
Author: Sebastian <sebasjm@taler-systems.com>
Date:   Wed,  1 Jul 2026 16:41:49 -0300

use binary instead of path

Diffstat:
Mpackages/taler-harness/README.md | 8+++-----
Mpackages/taler-harness/src/harness/harness.ts | 12------------
2 files changed, 3 insertions(+), 17 deletions(-)

diff --git a/packages/taler-harness/README.md b/packages/taler-harness/README.md @@ -41,14 +41,12 @@ Chrome: https://googlechromelabs.github.io/chrome-for-testing/ 3) The integration tests will expect the driver+browser available on PATH -If there are multiple binaries on the system the BROWSER_PATH environment variable -can be used to narrow the search path. This environment will replace the PATH -environment for the driver so it will limit the scope of -search for the driver and the browser. +If there are multiple binaries on the system the BROWSER_BINARY environment variable +can be used to specify the browser. For example ``` -export BROWSER_PATH=/opt/browsers/chrome/linux-145.0.7632.45/chrome-linux64/ +export BROWSER_BINARY=/opt/browsers/chrome/linux-145.0.7632.45/chrome-linux64/chrome taler-harness run-integrationtests web-merchant-login ``` diff --git a/packages/taler-harness/src/harness/harness.ts b/packages/taler-harness/src/harness/harness.ts @@ -2299,12 +2299,6 @@ export class BrowserService { profileDir, ], `web-browser`, - process.env.BROWSER_PATH - ? { - ...process.env, - PATH: process.env.BROWSER_PATH, - } - : undefined, ); break; } @@ -2319,12 +2313,6 @@ export class BrowserService { `--log-path=${this.globalState.testDir}/browser.log`, ], `web-browser`, - process.env.BROWSER_PATH - ? { - ...process.env, - PATH: process.env.BROWSER_PATH, - } - : undefined, ); break; }