feat: add E2E_TEST_UTILS_GIT_REF support to run-e2e.sh#2390
Conversation
0cf18ae to
d918933
Compare
|
/test ? |
|
/test e2e-ocp-helm-nightly |
❌ Failed Nightly E2E TestsPlatform: ocp 4.18 | RHDH Version: 1.10 | Duration: 31m 27s |
d918933 to
dc25df6
Compare
Assisted-by: Claude Code Co-Authored-By: Claude Code <noreply@anthropic.com>
dc25df6 to
40efe82
Compare
|
/test e2e-ocp-helm-nightly |
|
✅ Passed Nightly E2E TestsPlatform: ocp 4.18 | RHDH Version: 1.10 | Duration: 30m 37s |
|
/publish |
|
Publish workflow has completed with success. Publishing process✅ Finished successfully.
Backstage Compatibility Check✅ All workspaces are compatible with the target Backstage version ( No action required. Metadata Validation✅ All metadata files validated successfully. Running e2e tests |
|
|
✅ Passed E2E Tests -
|
| } | ||
|
|
||
| test.describe("TechDocs", () => { | ||
| test.describe.skip("TechDocs", () => { |
There was a problem hiding this comment.
Just for reference in case anyone else comes looking, there is a PR opened here to fix these tests: #2378. Skipping for now as they are continuously failing on nightly and the PR is still being actively worked on



Summary
Adds `E2E_TEST_UTILS_GIT_REF` support to `run-e2e.sh` — enables cloning and building `e2e-test-utils` from an unpublished git branch without needing an npm release first.
Motivation
When developing `rhdh-e2e-test-utils` changes that require overlay-side validation (e.g. new nightly mode behaviour, new fixtures), there was no way to wire a pre-release branch into the overlay test runner without a workaround. This fills that gap as a permanent, general-purpose escape hatch.
Usage
Related
Test plan
Assisted-by: Claude Code