AirfieldpathOrlando Sanford International

5.16 · The Interchange · Code

Tests

81 tests in 12 files. 81 pass at the time this site was built.

Level 2 of 3 This component, complete on its own. Its files, sources and tests are the detail below. Open the detail

Run with node --test in the repository. The count and the pass count above are read from that run when the site is built.

Test names (75)
FileTest
bhs.test.mjsthe BHS gateway: the payload is classified straight to baggage.conveyor.blocked and takes its path to alert, ticket, work order and the twin
bhs.test.mjsthe BHS alert is acknowledged, and escalates when nobody does
bhs.test.mjsnothing is dropped: bad signatures, unknown sources, unmatched codes, repeats and bad JSON stay visible
bhs.test.mjsa source key that is not configured rejects the item and says so
bhs.test.mjswithout a desk, the ticket waits with the reason
catalogue.test.mjsthe catalogue mapping is data, checked against its contract
catalogue.test.mjsinstalled items and models become fixture objects; each placement a proposed install issue linked to its item
catalogue.test.mjsany transport but the fixture site is refused, so no live Jira call is made
catalogue.test.mjsan option the plan does not have is refused by name
contracts.test.mjsthe contracts: the six kinds and the rest, plus MissionSight stream events
contracts.test.mjsevery file in ${d} passes ${name}
contracts.test.mjsevery template passes load_template, and the pipeline passes pipeline
contracts.test.mjsa reading passes the reading contract and names a catalogue type
documents.test.mjsa policy PDF drop: stored, text extracted, a document event, rules marked designed, the review checklist
documents.test.mjsa PDF with no text layer says so, and is still stored and classified
documents.test.mjsa file the drop has no rule for is kept as unclassified
documents.test.mjsa video capture is stored and becomes MissionSight's segment.stored, checked against MissionSight's schema
hub.test.mjscredentials: read from the active galaxy .env as StellarView reads them, never shown
hub.test.mjstransports: not configured fails visibly; live refuses without a test project named, before any call
hub.test.mjsconformance on the fixture site: the Assets schema, types and attributes from mappings/types.json, then objects
hub.test.mjsconformance on the fixture site: an issue linked to its Assets object, moved by status name, commented
hub.test.mjswebhooks: the signature is checked, and a status change is normalised to the hub message
hub.test.mjsrules: deterministic, disabled rules say why, a map gap and a conflict stop the message
hub.test.mjsmappings: each with its version, sha256 and source
hub.test.mjsi3: with its interface unknown (Q-35) every call fails visibly, and a confirmed work order stays proposed
hub.test.mjsthe round trip on fixtures: alarm to Jira and Assets, approval to i3, completion back, AI asked, a person accepts
hub.test.mjsa hop that cannot reach its system is retried, then parked with its error, and resumes on retry
hub.test.mjswith the hub on and no Jira site configured, the hub waits visibly and parks; the ticket listener stands aside
hub.test.mjsa webhook without the right signature is refused
interval.test.mjsa threshold the Studio has not confirmed never fires and is listed as a gap; after the confirmation the next alarm fires once, with the numbers
interval.test.mjswith no Studio export loaded, every threshold is a gap
interval.test.mjsa confirmed threshold with a parameter not set is a gap, never a default
interval.test.mjsthe old owner-set route is gone: thresholds come only from the Studio export
jira.test.mjslive mode is an interface only: it refuses and names what a live test needs
jira.test.mjsstub mode refuses any address that is not loopback
jira.test.mjsstates come back by the mapping in data; acceptance is an assignee; an unknown status is unmapped
jira.test.mjsthe CLI with --live refuses with the same message
kone.test.mjsKONE status: a stop is vt.escalator.stopped on Escalator 3, takes the vt-stopped path, and the ticket comes back accepted
kone.test.mjsa stop reason the mapping does not name is unclassified, never guessed
kone.test.mjsprediction: three stops on one escalator inside 24 hours raise vt.escalator.repeat_fault and propose a work request
kone.test.mjsprediction: three stops spread over 25 hours raise nothing
loads.test.mjsa template sheet loads: each row an asset record, every field loaded
loads.test.mjsa sheet that does not match stops the whole load and names each row and column
loads.test.mjsa sheet missing a column stops at the header
loads.test.mjsthe generated workbook template round-trips: filled in and loaded back
loads.test.mjsi3 asset export (provisional columns) maps to asset records
loads.test.mjsan i3 export with an unknown asset type or a date in the wrong form stops, naming the i3 column
loads.test.mjsi3 work order export maps to work orders
loads.test.mjsAllen-Bradley L5X: matched tags become sensor points, the rest are listed as unmatched
loads.test.mjsAllen-Bradley RSLogix tag CSV: TAG rows only, remarks and comments skipped
loads.test.mjsBMS point list, ${vendor}: points to sensor points; a unit the catalogue lacks is listed, not converted
loads.test.mjsa BMS vendor with no mapping stops the load and names the vendors there are
paths.test.mjsthe more specific path wins: vt-stopped names the type and a severity; the defaults only a severity
paths.test.mjswith equal specificity, the higher priority wins; with equal priority, the id decides
paths.test.mjsa path pinned by the trigger wins over a more specific one
paths.test.mjsan additive path runs beside the chosen one, here by the hour in Sanford
paths.test.mjsan info event with no path takes none, and says so
paths.test.mjsevery chosen path carries its policy link, linked or still to link
sensors.test.mjsa sensor's own fault is about the sensor asset, and goes to the sensor's owner
sensors.test.mjsa reading names the target as its asset, with the snapshot and its age, and the sensor as its source
sensors.test.mjsa device no sensor is bound to is kept, with the asset not mapped
sensors.test.mjstwo sensors on one device: the one whose type raises the event is chosen
sensors.test.mjsevery sensor asset passes the asset contract, and a trend input from a summary point is refused at load
sensors.test.mjsthe snapshots in data/sensors match the asset copy they were refreshed from
trapping.test.mjsrelay to Collector: a carousel BLOCKED state is trapped as baggage.carousel.blocked about the carousel, from its sensor
trapping.test.mjsvalue: chilled water below its limit is trapped; inside the limits it traps nothing and still goes on to history
trapping.test.mjsa reading in the wrong unit is rejected, never converted
trapping.test.mjstrend: the filter pressure drop rising over its window is trapped, from a point kept in full
trapping.test.mjsother: an escalator stop with reason safety_trip is trapped as vt.escalator.safety_stop and outranks the plain stop
trapping.test.mjsarea: an E-stop on level L1 is trapped as activity in a watched zone
trapping.test.mjsimage: a lens finding that differs is trapped and takes the path its trigger pins
trapping.test.mjsai: a model judgement waits for a person; only a confirmation raises the event (stub judge, no model called)
trapping.test.mjstime, silence: a sensor silent past its limit raises its own offline event, about the sensor asset
trapping.test.mjstime, schedule: a round falls due once per period
trapping.test.mjsthe relay buffers while the link is down and forwards in order when it returns