Documentation
¶
Overview ¶
Package coverage records, for every workflow kind the generator emits, the executing coverage that exercises it: e2e scenarios, e2e harness tests, and fleet lanes. The map is a positive record of what runs each generated workflow. A companion test derives the full set of emitted workflow kinds from the generator source and fails when an emitted kind has no entry here, so a new generated workflow cannot ship without a scenario or lane that runs it.
Index ¶
Constants ¶
This section is empty.
Variables ¶
var KnownFleetLanes = map[string]struct{}{
"primary": {},
"artifact-a": {},
"artifact-b": {},
"4env": {},
"3env": {},
"2env": {},
"single-env": {},
"release-only": {},
"no-env": {},
"callbacks": {},
"rollback-dispatch": {},
"monorepo": {},
}
KnownFleetLanes is the canonical fleet roster, mirroring the single source of truth in .github/workflows/fleet-e2e.yaml (the Select lanes step). A fleet lane reference in the registry must name one of these.
Functions ¶
This section is empty.
Types ¶
type Coverage ¶
type Coverage struct {
Summary string `yaml:"summary"`
Scenarios []string `yaml:"scenarios,omitempty"`
E2ETests []string `yaml:"e2e_tests,omitempty"`
FleetLanes []string `yaml:"fleet_lanes,omitempty"`
}
Coverage lists the executing references that exercise a single workflow kind. A kind is covered when it names at least one scenario, harness test, or fleet lane that runs the generated workflow.
Source Files