You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
const body = `:warning: \n[Test workflow](${runUrl}) skipped because some plugin metadata files (\`<workspace>/metadata/*.yaml\`) were not found.\n\nAdd the corresponding metadata files to enable testing for this workspace.\n`;
body = `:warning: \n[Test workflow](${runUrl}) skipped because some plugin configurations contain environment variables but the workspace \`tests/test.env\` file is missing.\n\nAdd the required \`test.env\` file to enable testing for this workspace.\n`;
281
+
} else {
282
+
body = `:warning: \n[Test workflow](${runUrl}) skipped because some plugin metadata files (\`<workspace>/metadata/*.yaml\`) were not found.\n\nAdd the corresponding metadata files to enable testing for this workspace.\n`;
Copy file name to clipboardExpand all lines: README.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,10 +133,15 @@ The repository includes an automated integration testing workflow that verifies
133
133
134
134
**Testing workflow steps:**
135
135
1.**Resolve metadata**: Retrieves published OCI references and PR metadata from the `published-exports` artifact
136
-
2.**Prepare test config**: Generates `dynamic-plugins.test.yaml` from plugin metadata and copies other configuration files (`tests/app-config.yaml` and workspace-specific `app-config.test.yaml`,`test.env`)
136
+
2.**Prepare test config**: Generates `dynamic-plugins.test.yaml` from plugin metadata and copies other configuration files (`tests/app-config.yaml`, workspace-specific `app-config.test.yaml` and`test.env`)
137
137
3.**Run integration tests**: Starts RHDH container with layered configuration, installs dynamic plugins from OCI artifacts, and verifies each plugin loads successfully
138
138
4.**Report results**: Posts test status as a commit status check and PR comment with pass/fail results and links to the workflow run
139
139
140
+
**Environment Variables in Tests:**
141
+
If your plugin configuration (in `metadata/*.yaml`) uses environment variables (e.g., `${API_TOKEN}`), you must provide them in a `test.env` file located at `workspaces/<workspace>/tests/test.env`.
142
+
- If the `.env` file is missing but required, tests are skipped.
143
+
- If the `.env` file exists but is missing variables, the workflow fails.
144
+
140
145
-**Results** are reported via PR comment and in the status check. The complete container logs are also available, in the `integration-tests/run` step.
0 commit comments