Green-Screen Testing with OL Terminal
Record session trails, replay captured TN3270/TN5250 traffic without the host, step-debug Hub Screens Flows, and run agent-driven green-screen tests over MCP.
Challenges
- Manual green-screen test setup is slow and inconsistent across repeated login and navigation paths.
- Live host access can make debugging and demonstrations hard to reproduce safely.
- Hub terminal Screens Flows need validation against real host behavior before integration teams rely on them.
Benefits
- Recorded trails and traffic captures give teams repeatable evidence for terminal behavior.
- Flow debugging shows screen changes, mapped fields, and outputs before APIs are finalized.
- Macros and MCP access help automate setup and agent-driven checks while preserving session context.
Centralized session admin and recording lets administrators and authorized users monitor live terminal sessions, preserve terminal activity as JSON trails, export screen-trail XML for OpenLegacy IDE compatibility, and review recorded snapshots. Teams can use recorded trails as evidence from real 3270 and 5250 work and replay a trail to compare host screens when validating terminal behavior.