Merge pull request #217 from HarperFast/integration-test-upd

updating integration test action versions, minor integration test uti…

Author: heskew

.github/workflows/integration-tests.yml

@@ -64,7 +64,7 @@ jobs:
         run: npm run build || true # we currently have type errors so just ignore that
 
       - name: Upload build artifacts
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@v7
         with:
           name: harper-build-artifacts-node-${{ matrix.node-version }}
           path: |
@@ -95,7 +95,7 @@ jobs:
           package-manager-cache: false
 
       - name: Download build artifacts
-        uses: actions/download-artifact@v4
+        uses: actions/download-artifact@v8
         with:
           name: harper-build-artifacts-node-${{ matrix.node-version }}
 
@@ -126,7 +126,7 @@ jobs:
 
       - name: Upload Harper logs
         if: steps.run-api-tests.outcome == 'failure'
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@v7
         with:
           name: harper-integration-api-test-logs-node-${{ matrix.node-version }}
           path: /tmp/hdb/log/hdb.log
@@ -155,7 +155,7 @@ jobs:
           package-manager-cache: false
 
       - name: Download build artifacts
-        uses: actions/download-artifact@v4
+        uses: actions/download-artifact@v8
         with:
           name: harper-build-artifacts-node-${{ matrix.node-version }}
 
@@ -167,7 +167,7 @@ jobs:
 
       - name: Upload Harper server logs
         if: failure()
-        uses: actions/upload-artifact@v4
+        uses: actions/upload-artifact@v7
         with:
           name: harper-server-logs-node-${{ matrix.node-version }}-shard-${{ matrix.shard }}
           path: /tmp/harper-integration-test-logs/

integrationTests/README.md

@@ -118,6 +118,30 @@ This option is used by the CI workflow and is useful for executing the same subs
 
 This option can be overridden using the `HARPER_INTEGRATION_TEST_SHARD` environment variable.
 
+### Server Log Capture
+
+When `HARPER_INTEGRATION_TEST_LOG_DIR` is set, each Harper instance writes its logs (`hdb.log`, `stdout.log`, `stderr.log`) to a per-suite subdirectory under the specified path. Directory names are derived from the suite name and loopback address (e.g. `Operations_Server-127_0_0_2/`).
+
+This is primarily designed for CI, where Harper's child process output is not visible in the GitHub Actions UI. On test failure, the log directory is uploaded as an artifact for debugging.
+
+**Important:** When this setting is active, it overrides any `logging.root` value in the Harper config passed via `options.config`. The suite log directory takes precedence so that logs are captured in a known, per-suite location.
+
+Logs from passing suites are automatically cleaned up on process exit. Only logs from failed suites are preserved.
+
+```sh
+# Local usage
+HARPER_INTEGRATION_TEST_LOG_DIR=/tmp/harper-test-logs npm run test:integration
+
+# Inspect logs after a failure
+ls /tmp/harper-test-logs/
+# Operations_Server-127_0_0_2/
+#   hdb.log
+#   stdout.log
+#   stderr.log
+```
+
+---
+
 #### `--only`
 
 > Equivalent to Node.js Test Runner's [`--test-only`](https://nodejs.org/docs/latest-v24.x/api/cli.html#--test-only) option.

integrationTests/utils/README.md

@@ -68,33 +68,19 @@ suite('My test suite', (ctx: ContextWithHarper) => {
 
 Configuration options for `setupHarper()`.
 
-**Interface Definition:**
-
 ```typescript
 export interface SetupHarperOptions {
-	/**
-	 * Timeout in milliseconds to wait for Harper to start.
-	 * @default 30000
-	 */
 	startupTimeoutMs?: number;
-	/**
-	 * Additional configuration options to pass to the Harper CLI.
-	 */
 	config: any;
-	/**
-	 * Environment variables to set when running Harper.
-	 */
 	env: any;
 }
 ```
 
 **Properties:**
 
-30000 (5 seconds), or the value of the `HARPER_INTEGRATION_TEST_STARTUP_TIMEOUT_MS` environment variable if set.
-
 - **`config`** - `object` (optional) - Additional configuration options to pass to the Harper CLI.
 - **`env`** - `object` (optional) - Additional environment variables to set when starting Harper.
-- **`startupTimeoutMs`** - `number` (optional) - Timeout in milliseconds to wait for Harper to start. Defaults to
+- **`startupTimeoutMs`** - `number` (optional) - Timeout in milliseconds to wait for Harper to start. Defaults to 30000, or the value of the `HARPER_INTEGRATION_TEST_STARTUP_TIMEOUT_MS` environment variable if set.
 
 **Environment Variables:**