AudioVideoPlayer Done
Instantiates the Ginga-HTML5 user agent's audio/video player and controls playback. Not applicable to Ginga-NCL.
Development tooling for the Atlantis team, not the official testing entry point. Nothing here is delivered to the
SGT. Project docs: docs/ONBOARDING.md.
One harness page per module. Each loads the module from common/modules/, exposes its public
methods and logs its events.
Instantiates the Ginga-HTML5 user agent's audio/video player and controls playback. Not applicable to Ginga-NCL.
UI module that shows, as on-screen buttons, the keys the tester can press at each interaction step.
UI module that shows the test case ID, the test-environment and receiver preconditions, and the tester actions.
Single-line message bar at the bottom of the screen; each message replaces the previous one; hidden when unused.
Table on the right side of the screen with the executed test cases and their result (Pass / Fail / Skipped, §6.5.9), paginated when it doesn't fit.
Handles requests to the TV 3.0 WebServices, for apps that use them as an accessory resource (not for apps whose goal is to verify those APIs). The harness runs the js variant against a mock of the WebServices.
Identity card of the G001–G003 filler applications (spec v0.1, 4.1): label, set marker, service name, virtual channel, application ID and color code. Not one of the §6.5.5 modules; to be declared to the SGT as an additional one.
Test flow shared by the Ginga-HTML5 test applications: preconditions, one tester action at a time, result, next case, over InformationBox, ButtonsBox, ResultsBox and NotificationBar. Not one of the §6.5.5 modules; to be declared to the SGT as an additional one.
Won't be developed. The Manual lists it for the Ginga CC WebServices of TV 2.X; by a suite decision the
suite provides only the TV30WebServices module (2026-09-29, docs/project/decisions.md).
Listed automatically: every application folder in applications/ shows up here once it exists
(/new-artifact creates it), with no change to this page. Open one in the viewer to run it with
an on-screen remote control and see its TestFlow state. Needs the dev server
(npm run dev:harness).
Each card shows the application at 1280×720, scaled down. The dark background stands in for the Persistent Media Player video. Open one full screen, or enter it from its tile in its group's BAMT parser demo below.
Parser demos that read XML signaling documents and draw the Application Catalog from them.
Fetches and parses actual XML signaling documents — three illustrative BAMTs modeled on the DVB AIT family
(the real NBR 25602 schema isn't in this repo) covering grouped-vs-expanded listing mode by icon count
(001_010: 45 icons; 001_011: 15 icons) and the always-visible grouping icon (001_012) — and draws
Application Catalog tiles purely from what's in each file, so you can edit a document and see the render
change. Clicking an app tile loads the app from TransportProtocol/@baseUrl; the G001 filler
apps it points to are the ones listed above.
Same approach, for Broadcaster W's optional grouping (B05, B06): two illustrative BAMTs that differ only in the filler pool (002_005: 12 icons, expanded; 002_009: 44 icons, grouped). On top of the render it simulates the individual favoriting of both cases: only the selected member is favorited, and its icon goes to the start of the favorites with the badge (ACFR-36). A simulation of the expected result, not evidence for the cases.