hsl1230/HTTP Forge Run Suite

Run an HTTP Forge test suite, collection, or folder and publish JUnit results. Exits non-zero when any test fails, so it can gate a CI build.

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stale
License: None

Inputs

name	description	required	default
workspace	Path to the HTTP Forge workspace folder (the directory that contains collections/, suites/, environments/). Relative to the repository root.	no	.
suite	Suite ID to run.	no	—
collection	Collection slug, id, or display name to run. Mutually exclusive with `suite` — provide exactly one of `suite`, `collection`, or `collection` + `folder`.	no	—
folder	Slash-separated folder path within the collection to run (e.g. "Auth/Login"). Requires `collection` to be set. When provided the action runs `run-folder` instead of `run-collection`.	no	""
recursive	Include nested sub-folders when running a folder (default: true). Set to "false" to run only the direct children of the folder.	no	true
environment	Environment name to activate (must exist in the workspace environments/ folder).	no	""
iterations	Number of iterations to run (default 1).	no	1
stop_on_error	Stop execution on the first failure.	no	false
reporters	Comma-separated list of reporter specs to enable. Each spec is either a reporter name (e.g. "junit") or a name with an explicit output path (e.g. "junit:test-results/junit.xml"). Supported names: html, junit. Example: "junit:test-results/junit.xml" or "html,junit:results/junit.xml"	no	junit:test-results/junit.xml
extra_args	Any additional raw CLI flags to append to the http-forge command, e.g. "--var BASE_URL=https://staging.example.com".	no	""
node_version	Node.js version to use (must be ≥ 20).	no	20
cli_version	@http-forge/cli npm version to install. Accepts any npm semver range, e.g. "latest", "0.2.x", "^0.2.0".	no	latest

Outputs

name	description
all_passed	"true" when every request assertion passed, "false" otherwise.