fixtures

type Fixture struct {
	// Dir under testdata/e2e (e.g. "hello", "volumes").
	Dir string
	// Pipeline is the pipeline name to run (a YAML may declare several).
	Pipeline string
	// Params for the pipeline run (key=value).
	Params map[string]string
	// WantStatus is the expected engine.RunResult.Status.
	WantStatus string
	// ConfigMaps maps name -> key -> inline value, seeded into the
	// configMap volumes.Store before the run.
	ConfigMaps map[string]map[string]string
	// Secrets is the same shape, seeded into the secret store.
	Secrets map[string]map[string]string
	// DockerOnly: skip in the cluster harness.
	DockerOnly bool
	// ClusterOnly: skip in the docker harness.
	ClusterOnly bool
	// Name is the Go subtest name used by t.Run; defaults to a derived form
	// when empty (see TestName).
	Name string
	// Description is a one-liner used in failure messages.
	Description string
	// WantResults, when non-nil, asserts engine.RunResult.Results is
	// equal (after a normalising pass — []string and []any with string
	// items count as equal, etc.) to this map. The cross-backend
	// fidelity guarantee for Pipeline.spec.results: both backends must
	// produce the same Results map for any fixture that sets this. If
	// nil, only WantStatus is asserted (the existing behavior).
	WantResults map[string]any
	// WantEventFields, if non-nil, asserts that for each named event
	// kind the first matching event in the captured stream carries
	// each named JSON-key/value pair. Shape:
	//   kind -> { jsonKey -> expectedValue }
	// Only the first event of each kind is inspected (run-start /
	// run-end always have exactly one; task-start / step-log are
	// asserted on the first emission). Skipped if the map is nil.
	WantEventFields map[string]map[string]string
	// Resolver, when non-empty, signals the e2e harness to:
	//   1. Spin up an httptest.Server before the run, serving files from
	//      testdata/e2e/<Dir>/served/.
	//   2. Configure engine.Options.Refresolver with a default registry
	//      whose `hub` resolver's BaseURL is rewritten to the test
	//      server (Resolver=="hub") or whose `http` resolver targets it
	//      via the fixture-server-url Pipeline param (Resolver=="http").
	//   3. Inject a fixture-server-url Pipeline param so the Pipeline's
	//      $(params.fixture-server-url) resolves at run time.
	// Phase 3 of Track 1 #9 wires these for cross-backend e2e coverage
	// of the hub + http direct resolvers; the cluster harness produces
	// the same inlined TaskSpec since resolution is client-side.
	// Empty value: not a resolver fixture (the existing behavior).
	Resolver string
}

type ResolverHarness struct {
	Server   *httptest.Server
	Registry *refresolver.Registry
	// ExtraParam is a single (name, value) tuple the caller MUST add to
	// the Pipeline's run params before invoking RunPipeline. For "http"
	// fixtures it carries the test server's base URL via
	// fixture-server-url; for "hub" fixtures the resolver targets the
	// server through Registry construction so this field is empty.
	// For "bundles" fixtures it carries the OCI ref the test
	// registry serves at, so the Pipeline's $(params.bundle-ref)
	// resolves to a working reference.
	ExtraParamName  string
	ExtraParamValue string
}