LTS-5452: README step to set credentials as env vars

.gitignore

@@ -1,6 +1,7 @@
 **/target/
 **/log
 **/browserstack-cli
+**/browserstack-cli.exe
 **/.DS_Store
 **/node_modules/
 **/yarn.lock

README.md

@@ -45,16 +45,16 @@
    - **Linux ARM**  
      [browserstack-cli-linux-arm](https://load-api.browserstack.com/api/v1/binary?os=linux&arch=arm64)
 
-   > The download is a zip. Extract it and place the `browserstack-cli` binary in the root of your project.
+   > The download is a zip. Extract it and place the `browserstack-cli` binary (`browserstack-cli.exe` on Windows) in the root of your project. On macOS or Linux, also run `chmod +x browserstack-cli`, since some unzip tools drop the executable bit.
 
 5. **Verify the BrowserStack CLI**
 
    Before running the binary, check that it is signed by BrowserStack:
 
-   - **macOS**: the output must include `TeamIdentifier=YQ5FZQ855D` (Browserstack Inc).
+   - **macOS**: the command must succeed. It only passes if an Apple-issued certificate for BrowserStack's team (`YQ5FZQ855D`) signed the binary.
 
      ```sh
-     codesign --verify --strict ./browserstack-cli && codesign -dv ./browserstack-cli 2>&1 | grep TeamIdentifier
+     codesign --verify --strict -R '=anchor apple generic and certificate leaf[subject.OU] = "YQ5FZQ855D"' ./browserstack-cli
      ```
 
    - **Windows** (PowerShell): `Status` must be `Valid` and the signer must be BrowserStack.
@@ -65,13 +65,40 @@
 
    If the check fails, do not run the binary.
 
-6. **Run tests using BrowserStack CLI**
+6. **Set your credentials**
+
+   The BrowserStack CLI reads your credentials from environment variables. Copy your username and access key from [Account Settings](https://www.browserstack.com/accounts/settings) and export them in the shell you run the test from:
+
+   On macOS or Linux (bash or zsh), run the lines below. The second one prompts for the key without echoing it, so the key stays out of your shell history:
+
+   ```sh
+   export BROWSERSTACK_USERNAME="<your-username>"
+   printf 'BrowserStack access key: '; read -rs BROWSERSTACK_ACCESS_KEY; echo; export BROWSERSTACK_ACCESS_KEY
+   ```
+
+   On Windows, run these in PowerShell. The second line prompts for the key in the same way:
+
+   ```powershell
+   $env:BROWSERSTACK_USERNAME = "<your-username>"
+   $env:BROWSERSTACK_ACCESS_KEY = [System.Net.NetworkCredential]::new('', (Read-Host -AsSecureString 'BrowserStack access key')).Password
+   ```
+
+   These variables last only for the current terminal session. If the CLI reports an authentication error, check that both are set in the terminal you run it from.
+
+   **Never commit your credentials.** Leave the `userName` and `accessKey` placeholders in `browserstack-load.yml` as they are (the environment variables override them), and keep your access key out of every file you push. If a key is ever exposed, regenerate it from Account Settings.
+
+7. **Run tests using BrowserStack CLI**
 
    ```sh
    ./browserstack-cli load run
    ```
 
-7. **View Test Results**
+   ```powershell
+   # Windows (PowerShell)
+   .\browserstack-cli.exe load run
+   ```
+
+8. **View Test Results**
 
    Visit the [BrowserStack Load-Testing Dashboard](https://load.browserstack.com/projects) to monitor and analyze your test runs.
 

java/README.md

@@ -39,16 +39,16 @@
    - **Linux ARM**  
      [browserstack-cli-linux-arm](https://load-api.browserstack.com/api/v1/binary?os=linux&arch=arm64)
 
-   > The download is a zip. Extract it and place the `browserstack-cli` binary in the root of your project.
+   > The download is a zip. Extract it and place the `browserstack-cli` binary (`browserstack-cli.exe` on Windows) in the root of your project. On macOS or Linux, also run `chmod +x browserstack-cli`, since some unzip tools drop the executable bit.
 
 4. **Verify the BrowserStack CLI**
 
    Before running the binary, check that it is signed by BrowserStack:
 
-   - **macOS**: the output must include `TeamIdentifier=YQ5FZQ855D` (Browserstack Inc).
+   - **macOS**: the command must succeed. It only passes if an Apple-issued certificate for BrowserStack's team (`YQ5FZQ855D`) signed the binary.
 
      ```sh
-     codesign --verify --strict ./browserstack-cli && codesign -dv ./browserstack-cli 2>&1 | grep TeamIdentifier
+     codesign --verify --strict -R '=anchor apple generic and certificate leaf[subject.OU] = "YQ5FZQ855D"' ./browserstack-cli
      ```
 
    - **Windows** (PowerShell): `Status` must be `Valid` and the signer must be BrowserStack.
@@ -59,13 +59,40 @@
 
    If the check fails, do not run the binary.
 
-5. **Run tests using BrowserStack CLI**
+5. **Set your credentials**
+
+   The BrowserStack CLI reads your credentials from environment variables. Copy your username and access key from [Account Settings](https://www.browserstack.com/accounts/settings) and export them in the shell you run the test from:
+
+   On macOS or Linux (bash or zsh), run the lines below. The second one prompts for the key without echoing it, so the key stays out of your shell history:
+
+   ```sh
+   export BROWSERSTACK_USERNAME="<your-username>"
+   printf 'BrowserStack access key: '; read -rs BROWSERSTACK_ACCESS_KEY; echo; export BROWSERSTACK_ACCESS_KEY
+   ```
+
+   On Windows, run these in PowerShell. The second line prompts for the key in the same way:
+
+   ```powershell
+   $env:BROWSERSTACK_USERNAME = "<your-username>"
+   $env:BROWSERSTACK_ACCESS_KEY = [System.Net.NetworkCredential]::new('', (Read-Host -AsSecureString 'BrowserStack access key')).Password
+   ```
+
+   These variables last only for the current terminal session. If the CLI reports an authentication error, check that both are set in the terminal you run it from.
+
+   **Never commit your credentials.** Leave the `userName` and `accessKey` placeholders in `browserstack-load.yml` as they are (the environment variables override them), and keep your access key out of every file you push. If a key is ever exposed, regenerate it from Account Settings.
+
+6. **Run tests using BrowserStack CLI**
 
    ```sh
    ./browserstack-cli load run
    ```
 
-6. **View Test Results**
+   ```powershell
+   # Windows (PowerShell)
+   .\browserstack-cli.exe load run
+   ```
+
+7. **View Test Results**
 
    Visit the [BrowserStack Load-Testing Dashboard](https://load.browserstack.com/projects) to monitor and analyze your test runs.
 

jest/README.md

@@ -39,16 +39,16 @@
    - **Linux ARM**  
      [browserstack-cli-linux-arm](https://load-api.browserstack.com/api/v1/binary?os=linux&arch=arm64)
 
-   > The download is a zip. Extract it and place the `browserstack-cli` binary in the root of your project.
+   > The download is a zip. Extract it and place the `browserstack-cli` binary (`browserstack-cli.exe` on Windows) in the root of your project. On macOS or Linux, also run `chmod +x browserstack-cli`, since some unzip tools drop the executable bit.
 
 4. **Verify the BrowserStack CLI**
 
    Before running the binary, check that it is signed by BrowserStack:
 
-   - **macOS**: the output must include `TeamIdentifier=YQ5FZQ855D` (Browserstack Inc).
+   - **macOS**: the command must succeed. It only passes if an Apple-issued certificate for BrowserStack's team (`YQ5FZQ855D`) signed the binary.
 
      ```sh
-     codesign --verify --strict ./browserstack-cli && codesign -dv ./browserstack-cli 2>&1 | grep TeamIdentifier
+     codesign --verify --strict -R '=anchor apple generic and certificate leaf[subject.OU] = "YQ5FZQ855D"' ./browserstack-cli
      ```
 
    - **Windows** (PowerShell): `Status` must be `Valid` and the signer must be BrowserStack.
@@ -59,13 +59,40 @@
 
    If the check fails, do not run the binary.
 
-5. **Run tests using BrowserStack CLI**
+5. **Set your credentials**
+
+   The BrowserStack CLI reads your credentials from environment variables. Copy your username and access key from [Account Settings](https://www.browserstack.com/accounts/settings) and export them in the shell you run the test from:
+
+   On macOS or Linux (bash or zsh), run the lines below. The second one prompts for the key without echoing it, so the key stays out of your shell history:
+
+   ```sh
+   export BROWSERSTACK_USERNAME="<your-username>"
+   printf 'BrowserStack access key: '; read -rs BROWSERSTACK_ACCESS_KEY; echo; export BROWSERSTACK_ACCESS_KEY
+   ```
+
+   On Windows, run these in PowerShell. The second line prompts for the key in the same way:
+
+   ```powershell
+   $env:BROWSERSTACK_USERNAME = "<your-username>"
+   $env:BROWSERSTACK_ACCESS_KEY = [System.Net.NetworkCredential]::new('', (Read-Host -AsSecureString 'BrowserStack access key')).Password
+   ```
+
+   These variables last only for the current terminal session. If the CLI reports an authentication error, check that both are set in the terminal you run it from.
+
+   **Never commit your credentials.** Leave the `userName` and `accessKey` placeholders in `browserstack-load.yml` as they are (the environment variables override them), and keep your access key out of every file you push. If a key is ever exposed, regenerate it from Account Settings.
+
+6. **Run tests using BrowserStack CLI**
 
    ```sh
    ./browserstack-cli load run
    ```
 
-6. **View Test Results**
+   ```powershell
+   # Windows (PowerShell)
+   .\browserstack-cli.exe load run
+   ```
+
+7. **View Test Results**
 
    Visit the [BrowserStack Load-Testing Dashboard](https://load.browserstack.com/projects) to monitor and analyze your test runs.
 

junit-4/README.md

@@ -39,16 +39,16 @@
    - **Linux ARM**  
      [browserstack-cli-linux-arm](https://load-api.browserstack.com/api/v1/binary?os=linux&arch=arm64)
 
-   > The download is a zip. Extract it and place the `browserstack-cli` binary in the root of your project.
+   > The download is a zip. Extract it and place the `browserstack-cli` binary (`browserstack-cli.exe` on Windows) in the root of your project. On macOS or Linux, also run `chmod +x browserstack-cli`, since some unzip tools drop the executable bit.
 
 4. **Verify the BrowserStack CLI**
 
    Before running the binary, check that it is signed by BrowserStack:
 
-   - **macOS**: the output must include `TeamIdentifier=YQ5FZQ855D` (Browserstack Inc).
+   - **macOS**: the command must succeed. It only passes if an Apple-issued certificate for BrowserStack's team (`YQ5FZQ855D`) signed the binary.
 
      ```sh
-     codesign --verify --strict ./browserstack-cli && codesign -dv ./browserstack-cli 2>&1 | grep TeamIdentifier
+     codesign --verify --strict -R '=anchor apple generic and certificate leaf[subject.OU] = "YQ5FZQ855D"' ./browserstack-cli
      ```
 
    - **Windows** (PowerShell): `Status` must be `Valid` and the signer must be BrowserStack.
@@ -59,13 +59,40 @@
 
    If the check fails, do not run the binary.
 
-5. **Run tests using BrowserStack CLI**
+5. **Set your credentials**
+
+   The BrowserStack CLI reads your credentials from environment variables. Copy your username and access key from [Account Settings](https://www.browserstack.com/accounts/settings) and export them in the shell you run the test from:
+
+   On macOS or Linux (bash or zsh), run the lines below. The second one prompts for the key without echoing it, so the key stays out of your shell history:
+
+   ```sh
+   export BROWSERSTACK_USERNAME="<your-username>"
+   printf 'BrowserStack access key: '; read -rs BROWSERSTACK_ACCESS_KEY; echo; export BROWSERSTACK_ACCESS_KEY
+   ```
+
+   On Windows, run these in PowerShell. The second line prompts for the key in the same way:
+
+   ```powershell
+   $env:BROWSERSTACK_USERNAME = "<your-username>"
+   $env:BROWSERSTACK_ACCESS_KEY = [System.Net.NetworkCredential]::new('', (Read-Host -AsSecureString 'BrowserStack access key')).Password
+   ```
+
+   These variables last only for the current terminal session. If the CLI reports an authentication error, check that both are set in the terminal you run it from.
+
+   **Never commit your credentials.** Leave the `userName` and `accessKey` placeholders in `browserstack-load.yml` as they are (the environment variables override them), and keep your access key out of every file you push. If a key is ever exposed, regenerate it from Account Settings.
+
+6. **Run tests using BrowserStack CLI**
 
    ```sh
    ./browserstack-cli load run
    ```
 
-6. **View Test Results**
+   ```powershell
+   # Windows (PowerShell)
+   .\browserstack-cli.exe load run
+   ```
+
+7. **View Test Results**
 
    Visit the [BrowserStack Load-Testing Dashboard](https://load.browserstack.com/projects) to monitor and analyze your test runs.
 

junit-5/README.md

@@ -39,16 +39,16 @@
    - **Linux ARM**  
      [browserstack-cli-linux-arm](https://load-api.browserstack.com/api/v1/binary?os=linux&arch=arm64)
 
-   > The download is a zip. Extract it and place the `browserstack-cli` binary in the root of your project.
+   > The download is a zip. Extract it and place the `browserstack-cli` binary (`browserstack-cli.exe` on Windows) in the root of your project. On macOS or Linux, also run `chmod +x browserstack-cli`, since some unzip tools drop the executable bit.
 
 4. **Verify the BrowserStack CLI**
 
    Before running the binary, check that it is signed by BrowserStack:
 
-   - **macOS**: the output must include `TeamIdentifier=YQ5FZQ855D` (Browserstack Inc).
+   - **macOS**: the command must succeed. It only passes if an Apple-issued certificate for BrowserStack's team (`YQ5FZQ855D`) signed the binary.
 
      ```sh
-     codesign --verify --strict ./browserstack-cli && codesign -dv ./browserstack-cli 2>&1 | grep TeamIdentifier
+     codesign --verify --strict -R '=anchor apple generic and certificate leaf[subject.OU] = "YQ5FZQ855D"' ./browserstack-cli
      ```
 
    - **Windows** (PowerShell): `Status` must be `Valid` and the signer must be BrowserStack.
@@ -59,13 +59,40 @@
 
    If the check fails, do not run the binary.
 
-5. **Run tests using BrowserStack CLI**
+5. **Set your credentials**
+
+   The BrowserStack CLI reads your credentials from environment variables. Copy your username and access key from [Account Settings](https://www.browserstack.com/accounts/settings) and export them in the shell you run the test from:
+
+   On macOS or Linux (bash or zsh), run the lines below. The second one prompts for the key without echoing it, so the key stays out of your shell history:
+
+   ```sh
+   export BROWSERSTACK_USERNAME="<your-username>"
+   printf 'BrowserStack access key: '; read -rs BROWSERSTACK_ACCESS_KEY; echo; export BROWSERSTACK_ACCESS_KEY
+   ```
+
+   On Windows, run these in PowerShell. The second line prompts for the key in the same way:
+
+   ```powershell
+   $env:BROWSERSTACK_USERNAME = "<your-username>"
+   $env:BROWSERSTACK_ACCESS_KEY = [System.Net.NetworkCredential]::new('', (Read-Host -AsSecureString 'BrowserStack access key')).Password
+   ```
+
+   These variables last only for the current terminal session. If the CLI reports an authentication error, check that both are set in the terminal you run it from.
+
+   **Never commit your credentials.** Leave the `userName` and `accessKey` placeholders in `browserstack-load.yml` as they are (the environment variables override them), and keep your access key out of every file you push. If a key is ever exposed, regenerate it from Account Settings.
+
+6. **Run tests using BrowserStack CLI**
 
    ```sh
    ./browserstack-cli load run
    ```
 
-6. **View Test Results**
+   ```powershell
+   # Windows (PowerShell)
+   .\browserstack-cli.exe load run
+   ```
+
+7. **View Test Results**
 
    Visit the [BrowserStack Load-Testing Dashboard](https://load.browserstack.com/projects) to monitor and analyze your test runs.
 

serenity-cucumber/README.md

@@ -39,16 +39,16 @@
    - **Linux ARM**  
      [browserstack-cli-linux-arm](https://load-api.browserstack.com/api/v1/binary?os=linux&arch=arm64)
 
-   > The download is a zip. Extract it and place the `browserstack-cli` binary in the root of your project.
+   > The download is a zip. Extract it and place the `browserstack-cli` binary (`browserstack-cli.exe` on Windows) in the root of your project. On macOS or Linux, also run `chmod +x browserstack-cli`, since some unzip tools drop the executable bit.
 
 4. **Verify the BrowserStack CLI**
 
    Before running the binary, check that it is signed by BrowserStack:
 
-   - **macOS**: the output must include `TeamIdentifier=YQ5FZQ855D` (Browserstack Inc).
+   - **macOS**: the command must succeed. It only passes if an Apple-issued certificate for BrowserStack's team (`YQ5FZQ855D`) signed the binary.
 
      ```sh
-     codesign --verify --strict ./browserstack-cli && codesign -dv ./browserstack-cli 2>&1 | grep TeamIdentifier
+     codesign --verify --strict -R '=anchor apple generic and certificate leaf[subject.OU] = "YQ5FZQ855D"' ./browserstack-cli
      ```
 
    - **Windows** (PowerShell): `Status` must be `Valid` and the signer must be BrowserStack.
@@ -59,13 +59,40 @@
 
    If the check fails, do not run the binary.
 
-5. **Run tests using BrowserStack CLI**
+5. **Set your credentials**
+
+   The BrowserStack CLI reads your credentials from environment variables. Copy your username and access key from [Account Settings](https://www.browserstack.com/accounts/settings) and export them in the shell you run the test from:
+
+   On macOS or Linux (bash or zsh), run the lines below. The second one prompts for the key without echoing it, so the key stays out of your shell history:
+
+   ```sh
+   export BROWSERSTACK_USERNAME="<your-username>"
+   printf 'BrowserStack access key: '; read -rs BROWSERSTACK_ACCESS_KEY; echo; export BROWSERSTACK_ACCESS_KEY
+   ```
+
+   On Windows, run these in PowerShell. The second line prompts for the key in the same way:
+
+   ```powershell
+   $env:BROWSERSTACK_USERNAME = "<your-username>"
+   $env:BROWSERSTACK_ACCESS_KEY = [System.Net.NetworkCredential]::new('', (Read-Host -AsSecureString 'BrowserStack access key')).Password
+   ```
+
+   These variables last only for the current terminal session. If the CLI reports an authentication error, check that both are set in the terminal you run it from.
+
+   **Never commit your credentials.** Leave the `userName` and `accessKey` placeholders in `browserstack-load.yml` as they are (the environment variables override them), and keep your access key out of every file you push. If a key is ever exposed, regenerate it from Account Settings.
+
+6. **Run tests using BrowserStack CLI**
 
    ```sh
    ./browserstack-cli load run
    ```
 
-6. **View Test Results**
+   ```powershell
+   # Windows (PowerShell)
+   .\browserstack-cli.exe load run
+   ```
+
+7. **View Test Results**
 
    Visit the [BrowserStack Load-Testing Dashboard](https://load.browserstack.com/projects) to monitor and analyze your test runs.