How stb-tester/stb-tester-test-pack works
Project type and purpose
• This is not a web app or microservice; it’s a test-automation “test-pack” built on top of the Stb-tester platform.
File structure
• Top‐level files/config:
• config/stbt.conf (Stb-tester version & settings)
• config/remote-control/roku.lircd.conf (IR codes for remote)
• stbt_rig.py (custom rig layer that encapsulates device communication)
• Tests directory:
• tests/roku/pages/... (page-object models for each screen)
• tests/roku/tests.py (actual test functions)
• Selftest folder: sample screenshots & self-validation assets
• CI/pytest.ini/.pylintrc: standard test runner & lint configs
README for additional insights
• Confirms:
• Tests are plain Python functions under tests/
• Version pinning in config/stbt.conf
Final checklist for the engineer
• Confirm you have:
• Notes on key patterns (Page Object, Config-Driven)
• An extensibility boundary showing where to add new tests or pages
• Keep it detailed but focused on the core architectural flow: Test Runner → Rig → Device → Artifacts.