Add loadtest-controller part of emulated browsers feature

Author: ivchicano

.github/workflows/openvidu-loadtest-e2e-dockerized-test.yml

@@ -28,7 +28,8 @@ jobs:
             exit 1
           fi
 
-          echo "ovurl=https://$LAN_PRIVATE_IP.openvidu-local.dev:7443" >> "$GITHUB_OUTPUT"
+          LAN_PRIVATE_IP_DASHED="${LAN_PRIVATE_IP//./-}"
+          echo "ovurl=https://$LAN_PRIVATE_IP_DASHED.openvidu-local.dev:7443" >> "$GITHUB_OUTPUT"
         
       - name: Run Browser Emulator E2E Tests in Docker
         env:
@@ -37,10 +38,10 @@ jobs:
           cd browser-emulator
           docker compose -f docker-compose.test.yml up --build --abort-on-container-exit --exit-code-from browser-emulator-tests          
 
-      - name: Run OpenVidu LoadTest E2E Tests
+      - name: Run All OpenVidu LoadTest E2E Tests
         run: |
           cd e2e-tests/scripts
-          ./run-smoke-test.sh ${{ steps.openvidu_env.outputs.ovurl }}
+          ./run-all-e2e-tests.sh ${{ steps.openvidu_env.outputs.ovurl }} devkey secret
       
       - name: Clean up
         if: always()

AGENTS.md

@@ -94,13 +94,20 @@ mvn spring-boot:run  # Start the controller
 ```bash
 cd e2e-tests
 
-# Run smoke test (requires OpenVidu instance)
-./scripts/run-smoke-test.sh <PLATFORM_URL> [APIKEY] [APISECRET]
+# Run all e2e tests (requires OpenVidu instance)
+./scripts/run-all-e2e-tests.sh <PLATFORM_URL> [APIKEY] [APISECRET]
+
+# Run central test runner with custom config
+./scripts/run-e2e-test.sh <CONFIG_FILE> <VALIDATION_SCRIPT> <PLATFORM_URL> [APIKEY] [APISECRET]
 
 # Direct Docker Compose
-docker-compose up --build
+docker compose up --build
 ```
 
+**Default credentials**: API key defaults to `devkey`, API secret defaults to `secret` if not provided.
+
+**Test discovery**: The unified runner (`run-all-e2e-tests.sh`) automatically discovers all `*-config.yaml` files in `config/` and maps them to validation scripts using convention: `foo-config.yaml` → `validate-foo.sh` (fallback: `validate-default.sh`).
+
 ## Code Style Guidelines
 
 ### TypeScript/JavaScript (Browser Emulator)

README.md

@@ -160,7 +160,7 @@ Define multiple test scenarios that run sequentially. Each test case can have th
 | `topology`                 | **Yes**  | -         | `N:N`, `N:M`, `TEACHING`, or `ONE_SESSION`                                                                 |
 | `participants`             | **Yes**  | -         | List of participant counts (e.g., `["2", "10"]`). Each element of the list will create a new test scenario |
 | `sessions`                 | **Yes**  | -         | Number of sessions or `infinite`                                                                           |
-| `browser`                  | No       | `chrome`  | Browser to use: `chrome` or `firefox`                                                                      |
+| `browser`                  | No       | `chrome`  | Browser to use: `chrome`, `firefox`, or `emulated`                                                                   |
 | `resolution`               | No       | `640x480` | Try to force video to resolution: `640x480`, `1280x720`, `1920x1080`                                       |
 | `frameRate`                | No       | `30`      | Try to force video frame rate                                                                              |
 | `startingParticipants`     | No       | `0`       | Adds a configurable initial batch of participants                                                          |

docker-compose.yml

@@ -33,8 +33,7 @@ services:
       MEDIAFILES_HOST_DIR: ${MEDIAFILES_HOST_DIR:-${PWD}/browser-emulator/mediafiles}
       SCRIPTS_LOGS_HOST_DIR: ${SCRIPTS_LOGS_HOST_DIR:-${PWD}/browser-emulator/logs}
       METRICBEAT_CONFIG: ${METRICBEAT_CONFIG:-${PWD}/browser-emulator/src/assets/metricbeat-config/metricbeat.yml}
-    ports:
-      - '5000:5000'
+    stop_grace_period: 60s
     networks:
       - browseremulator
     volumes:

e2e-tests/README.md

@@ -14,63 +14,93 @@ This directory contains end-to-end tests that validate the complete OpenVidu Loa
 2. An OpenVidu instance available for testing (you can use a local development installation)
 3. The OpenVidu instance URL, API key, and API secret
 
-## Smoke Test
+## Script Architecture
 
-The smoke test performs a basic end-to-end test with 2 participants in a single session using the N:N topology.
+The e2e test scripts follow a modular architecture:
 
-### Configuration
+- **`run-all-e2e-tests.sh`** - Unified test runner that discovers and runs all tests sequentially
+- **`run-e2e-test.sh`** - Central test runner for a single test (called by unified runner)
+- **`validate-default.sh`** - Default validation script for smoke test expectations
 
-The smoke test script accepts command-line arguments for OpenVidu connection details:
+## Running All Tests
+
+To run all e2e tests in one command:
 
 ```bash
 cd e2e-tests/scripts
-./run-smoke-test.sh <PLATFORM_URL> [PLATFORM_APIKEY] [PLATFORM_APISECRET]
-```
+./run-all-e2e-tests.sh <PLATFORM_URL> [API_KEY] [API_SECRET]
 
-Where:
+# Example
+./run-all-e2e-tests.sh https://172-31-224-178.openvidu-local.dev:7443 devkey secret
+```
 
-- `PLATFORM_URL`: Required. The URL of your OpenVidu deployment (e.g., https://your-openvidu-url.io:7443)
-- `PLATFORM_APIKEY`: Optional. API key for authentication (defaults to "devkey")
-- `PLATFORM_APISECRET`: Optional. API secret for authentication (defaults to "secret")
+The unified runner will:
 
-### Configuration File
+1. Discover all `*-config.yaml` files in the `config/` directory
+2. Map each config to its validation script using convention (see below)
+3. Run each test sequentially
+4. Print a summary of all test results
 
-The smoke test uses the configuration file `config/smoke-test-config.yaml` which specifies `advanced.reportOutput: html,txt` to generate both text and HTML reports.
+## Running Individual Tests
 
-### Running the Smoke Test
+### Smoke Test (Chrome)
 
 ```bash
-# Example with all parameters
 cd e2e-tests/scripts
-./run-smoke-test.sh https://your-openvidu-url.io:7443 myapikey myapisecret
+./run-e2e-test.sh emulated-smoke-test-config.yaml validate-default.sh <PLATFORM_URL> [API_KEY] [API_SECRET]
+```
+
+### Emulated Browser Test
 
-# Example with defaults for API key and secret
+```bash
 cd e2e-tests/scripts
-./run-smoke-test.sh https://your-openvidu-url.io:7443
+./run-e2e-test.sh smoke-test-config.yaml validate-default.sh <PLATFORM_URL> [API_KEY] [API_SECRET]
 ```
 
-This script will:
+## Test Discovery and Validation Mapping
+
+The unified runner uses convention-based mapping to determine which validation script to use for each config file:
+
+1. For a config file named `foo-config.yaml`, the runner looks for `validate-foo.sh`
+2. If a specific validation script is not found, it falls back to `validate-default.sh`
+
+**Example:**
+
+- `smoke-test-config.yaml` → looks for `validate-smoke-test.sh` → falls back to `validate-default.sh`
+- `emulated-smoke-test-config.yaml` → looks for `validate-emulated-smoke-test.sh` → falls back to `validate-default.sh`
+
+## Adding New Test Types
 
-1. Start both services using Docker Compose
-2. Wait for the test to complete
-3. Stop the services
-4. Display and validate the test results
+To add a new test type:
 
-### Expected Results
+1. **Create a configuration file** in `config/` (e.g., `my-test-config.yaml`)
 
-The test should:
+2. **Optionally create a validation script** in `scripts/` if the expected results differ from the default:
+   - Name it `validate-my-test.sh` (matching the config name without `-config.yaml`)
+   - If not created, `validate-default.sh` will be used automatically
+
+3. **No workflow changes needed** - the unified runner automatically discovers and runs all config files
+
+## Configuration-Validation Mapping Examples
+
+| Config file                       | Validation script (if exists)     | Fallback              |
+| --------------------------------- | --------------------------------- | --------------------- |
+| `smoke-test-config.yaml`          | `validate-smoke-test.sh`          | `validate-default.sh` |
+| `emulated-smoke-test-config.yaml` | `validate-emulated-smoke-test.sh` | `validate-default.sh` |
+| `load-test-config.yaml`           | `validate-load-test.sh`           | `validate-default.sh` |
+
+## Expected Results
+
+All smoke tests should:
 
 - Start both loadtest-controller and browser-emulator services
-- Launch 2 Chrome browsers that connect to the OpenVidu instance
 - Create a single session with 2 participants in N:N topology
 - Generate results in the `results/` directory:
   - `results.txt` (text summary)
-  - `report.html` (HTML report, with user retry details if retries occurred)
+  - `report.html` (HTML report)
 - Complete successfully and shut down cleanly
 
-### Validation Checks
-
-The smoke test validates that both `results.txt` and `report.html` files are generated and contain expected content.
+### Validation Checks (Default)
 
 **results.txt validation:**
 
@@ -87,26 +117,13 @@ The smoke test validates that both `results.txt` and `report.html` files are gen
 - "Sessions Created"
 - "Total Participants"
 - "User Connections" (mandatory)
-- Table columns: User, Session, Join date (from successful connection), Disconnect Date (captured from ParticipantDisconnected websocket event), Retry Number (count of retries per user)
+- Table columns: User, Session, Join date, Disconnect Date, Retry Number
 - Two user rows (User1 and User2) present
 
-The smoke test configuration uses `advanced.reportOutput: html,txt` to generate both output formats. If validation fails, the result files are kept in the `results/` directory for debugging.
-
-## Extending the Test Suite
-
-Additional test scenarios can be added by:
-
-1. Creating new configuration files in `configs/` directory
-2. Adding new scripts in `scripts/` directory or modifying the existing one
-3. Following the same pattern as the smoke test
-
-Examples of additional test scenarios:
-
-- Scaling tests with different participant counts
-- Different topologies (N:M, TEACHING, etc.)
-- Different browsers (Chrome vs Firefox)
+If validation fails, the result files are kept in the `results/` directory for debugging.
 
 ## Notes
 
 - Make sure your OpenVidu instance is accessible from the Docker containers
-- For troubleshooting, check the Docker Compose logs with `docker-compose logs`
+- For troubleshooting, check the Docker Compose logs with `docker compose logs`
+- Tests run sequentially to avoid resource conflicts

e2e-tests/config/emulated-smoke-test-config.yaml

@@ -0,0 +1,25 @@
+# yaml-language-server: $schema=../../schema/openvidu-loadtest-schema.json
+platform:
+  url: https://to-be-replaced:7443
+  apiKey: devkey
+  apiSecret: secret
+
+testcases:
+  - topology: N:N
+    participants:
+      - "2"
+    sessions: 1
+    browser: emulated
+    description: "Basic N:N topology test with emulated browsers"
+
+workers:
+  urls: 
+    - browser-emulator
+
+distribution:
+  usersPerWorker: 2
+
+advanced:
+  reportOutput:
+    - html
+    - txt

e2e-tests/docker-compose.yml

@@ -30,11 +30,15 @@ services:
     container_name: browser-emulator-e2e
     restart: no
     environment:
-      RUNNING_IN_DOCKER: true
-      DOCKER_NETWORK_NAME: browseremulator-e2e
-      DOCKER_BROWSER_EMULATOR_HOST: browser-emulator
-      MEDIAFILES_HOST_DIR: ${MEDIAFILES_HOST_DIR:-${PWD}/../../browser-emulator/mediafiles}
-      SCRIPTS_LOGS_HOST_DIR: ${SCRIPTS_LOGS_HOST_DIR:-${PWD}/../../browser-emulator/logs}
+        SERVER_PORT: ${SERVER_PORT:-5000}
+        WEBSOCKET_PORT: ${WEBSOCKET_PORT:-5001}
+        RUNNING_IN_DOCKER: true
+        DOCKER_NETWORK_NAME: browseremulator-e2e
+        DOCKER_BROWSER_EMULATOR_HOST: browser-emulator
+        MEDIAFILES_HOST_DIR: ${MEDIAFILES_HOST_DIR}
+        SCRIPTS_LOGS_HOST_DIR: ${SCRIPTS_LOGS_HOST_DIR}
+        METRICBEAT_CONFIG: ${METRICBEAT_CONFIG}
+    stop_grace_period: 60s
     networks:
       - browseremulator
     volumes:

e2e-tests/scripts/run-all-e2e-tests.sh

@@ -0,0 +1,120 @@
+#!/bin/bash
+
+# Unified e2e test runner for OpenVidu Load Test
+# This script discovers and runs all e2e tests sequentially
+# Usage: ./run-all-e2e-tests.sh <PLATFORM_URL> [API_KEY] [API_SECRET]
+# Example: ./run-all-e2e-tests.sh https://172-31-224-178.openvidu-local.dev:7443 devkey secret
+
+set -e
+
+echo "Starting OpenVidu Load Test E2E Test Suite..."
+
+# Check if docker compose is available
+if ! command -v docker compose &> /dev/null; then
+    echo "docker compose not found. Please install docker compose."
+    exit 1
+fi
+
+# Check arguments
+if [ $# -lt 1 ]; then
+    echo "Usage: $0 <PLATFORM_URL> [API_KEY] [API_SECRET]"
+    echo "Example: $0 https://openvidu.example.com:7443 devkey secret"
+    exit 1
+fi
+
+PLATFORM_URL="$1"
+PLATFORM_APIKEY="${2:-devkey}"
+PLATFORM_APISECRET="${3:-secret}"
+
+# Configuration
+SCRIPT_DIR="$(dirname "$(realpath "$0")")"
+E2E_TEST_DIR="$(realpath "$SCRIPT_DIR/..")"
+CONFIG_DIR="$E2E_TEST_DIR/config"
+DEFAULT_VALIDATION="validate-default.sh"
+
+# Discover all config files
+CONFIG_FILES=()
+for config in "$CONFIG_DIR"/*.yaml; do
+    if [ -f "$config" ]; then
+        CONFIG_FILES+=("$config")
+    fi
+done
+
+if [ ${#CONFIG_FILES[@]} -eq 0 ]; then
+    echo "ERROR: No configuration files found in $CONFIG_DIR"
+    exit 1
+fi
+
+echo "Found ${#CONFIG_FILES[@]} test configuration(s)"
+
+# Track test results
+TOTAL_TESTS=0
+PASSED_TESTS=0
+FAILED_TESTS=0
+FAILED_TEST_NAMES=()
+
+# Run each test
+for config_path in "${CONFIG_FILES[@]}"; do
+    config_file="$(basename "$config_path")"
+    
+    # Extract test name: e.g., "smoke-test" from "smoke-test-config.yaml"
+    test_name="$(echo "$config_file" | sed 's/-config\.yaml$//')"
+    
+    # Determine validation script using convention:
+    # Look for validate-<test-name>.sh, fallback to validate-default.sh
+    specific_validation="validate-${test_name}.sh"
+    if [ -f "$SCRIPT_DIR/$specific_validation" ]; then
+        validation_script="$specific_validation"
+    else
+        validation_script="$DEFAULT_VALIDATION"
+    fi
+    
+    if [ ! -f "$SCRIPT_DIR/$validation_script" ]; then
+        echo "ERROR: Validation script not found: $validation_script"
+        exit 1
+    fi
+    
+    TOTAL_TESTS=$((TOTAL_TESTS + 1))
+    
+    echo ""
+    echo "========================================"
+    echo "Running test $TOTAL_TESTS: $test_name"
+    echo "  Config: $config_file"
+    echo "  Validation: $validation_script"
+    echo "========================================"
+    echo ""
+    
+    # Run the test
+    if bash "$SCRIPT_DIR/run-e2e-test.sh" "$config_file" "$validation_script" "$PLATFORM_URL" "$PLATFORM_APIKEY" "$PLATFORM_APISECRET"; then
+        echo "✓ Test '$test_name' PASSED"
+        PASSED_TESTS=$((PASSED_TESTS + 1))
+    else
+        echo "✗ Test '$test_name' FAILED"
+        FAILED_TESTS=$((FAILED_TESTS + 1))
+        FAILED_TEST_NAMES+=("$test_name")
+    fi
+done
+
+# Print summary
+echo ""
+echo "========================================"
+echo "E2E Test Suite Summary"
+echo "========================================"
+echo "Total tests: $TOTAL_TESTS"
+echo "Passed: $PASSED_TESTS"
+echo "Failed: $FAILED_TESTS"
+
+if [ $FAILED_TESTS -gt 0 ]; then
+    echo ""
+    echo "Failed tests:"
+    for name in "${FAILED_TEST_NAMES[@]}"; do
+        echo "  - $name"
+    done
+    echo ""
+    echo "E2E Test Suite FAILED"
+    exit 1
+fi
+
+echo ""
+echo "E2E Test Suite PASSED"
+exit 0