aethyr/Aethyr
aethyr/Aethyr
2
0
Fork 0
Code Issues 281 Pull requests Projects Releases Packages Wiki Activity Actions

feat: implement HeadlessRenderer for terminal-free UI testing #324

Merged
freemo merged 3 commits from feature/m2-headless-renderer into master 2026-03-16 19:56:16 +00:00
Conversation 0 Commits 3 Files changed 6 +1152
freemo commented 2026-03-16 16:32:43 +00:00
Owner
Copy link

Summary

  • Implements HeadlessRenderer class as drop-in replacement for Ncurses/Composite stages in tests
  • Captures rendered output in memory for UI testing without terminal dependency
  • Provides test helpers for Cucumber step definitions via HeadlessRendererHelper module

Key Features

  • window_content(window_name) - returns content array for a window
  • last_frame - returns hash of all window contents from last frame
  • frame_count - tracks total frames rendered
  • clear_history - resets all captured state
  • last_bar_update(bar_name) - convenience method for status bar assertions
  • content_includes?(window, text) and bar_equals?(bar, value, max) test helpers
  • Auto-detection via HeadlessRenderer.headless_environment? when TERM unset or HEADLESS=1

Testing

  • 24 unit test scenarios (all passing)
  • 4 integration test scenarios (all passing)

Related

Closes #309

## Summary - Implements `HeadlessRenderer` class as drop-in replacement for Ncurses/Composite stages in tests - Captures rendered output in memory for UI testing without terminal dependency - Provides test helpers for Cucumber step definitions via `HeadlessRendererHelper` module ## Key Features - `window_content(window_name)` - returns content array for a window - `last_frame` - returns hash of all window contents from last frame - `frame_count` - tracks total frames rendered - `clear_history` - resets all captured state - `last_bar_update(bar_name)` - convenience method for status bar assertions - `content_includes?(window, text)` and `bar_equals?(bar, value, max)` test helpers - Auto-detection via `HeadlessRenderer.headless_environment?` when TERM unset or HEADLESS=1 ## Testing - 24 unit test scenarios (all passing) - 4 integration test scenarios (all passing) ## Related Closes #309
freemo force-pushed feature/m2-headless-renderer from 1761d434db to 9ea7759011
Some checks failed
CI / lint (pull_request) Failing after 14s
Details
CI / unit_tests (pull_request) Failing after 14s
Details
CI / integration_tests (pull_request) Failing after 17s
Details
CI / build (pull_request) Has been skipped
Details
2026-03-16 16:57:55 +00:00 Compare
freemo force-pushed feature/m2-headless-renderer from 9ea7759011
Some checks failed
CI / lint (pull_request) Failing after 14s
Details
CI / unit_tests (pull_request) Failing after 14s
Details
CI / integration_tests (pull_request) Failing after 17s
Details
CI / build (pull_request) Has been skipped
Details
to 197653ce8a
Some checks failed
CI / lint (pull_request) Failing after 39s
Details
CI / integration_tests (pull_request) Failing after 47s
Details
CI / unit_tests (pull_request) Failing after 9m47s
Details
CI / build (pull_request) Has been skipped
Details
2026-03-16 17:32:37 +00:00 Compare
freemo force-pushed feature/m2-headless-renderer from 197653ce8a
Some checks failed
CI / lint (pull_request) Failing after 39s
Details
CI / integration_tests (pull_request) Failing after 47s
Details
CI / unit_tests (pull_request) Failing after 9m47s
Details
CI / build (pull_request) Has been skipped
Details
to e34f38212e
Some checks failed
CI / lint (push) Waiting to run
Details
CI / unit_tests (push) Waiting to run
Details
CI / integration_tests (push) Waiting to run
Details
CI / build (push) Blocked by required conditions
Details
CI / lint (pull_request) Failing after 40s
Details
CI / integration_tests (pull_request) Failing after 49s
Details
CI / unit_tests (pull_request) Failing after 11m40s
Details
CI / build (pull_request) Has been skipped
Details
2026-03-16 19:56:06 +00:00 Compare
freemo merged commit e34f38212e into master 2026-03-16 19:56:16 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Blocked
Cannot proceed, depends on unresolved issue

  
Duplicate
Issue is a duplicate of an existing one

  
MoSCoW/Could Have
Desirable but not necessary, included if time permits

  
MoSCoW/Must Have
Essential, project cannot ship without it

  
MoSCoW/Should Have
Important but not strictly essential

  
Points/1
Estimated effort: 1 story points

  
Points/13
Estimated effort: 13 story points

  
Points/2
Estimated effort: 2 story points

  
Points/21
Estimated effort: 21 story points

  
Points/3
Estimated effort: 3 story points

  
Points/5
Estimated effort: 5 story points

  
Points/8
Estimated effort: 8 story points

  
Priority/Backlog
Not yet prioritized

  
Priority/Critical
Must be addressed immediately

  
Priority/High
Important, should be completed soon

  
Priority/Low
Nice to have, not time-sensitive

  
Priority/Medium
Normal priority, valid and should be addressed

  
State/Completed
Issue resolved and all PRs merged

  
State/In progress
Someone is actively working on this issue

  
State/In review
Implementation complete, PR submitted for review

  
State/Paused
Work temporarily suspended, typically blocked

  
State/Unverified
Issue created but not yet reviewed by a maintainer

  
State/Verified
Maintainer confirmed valid and actionable

  
State/Wont Do
Deliberate decision not to address this issue

  
Type/Bug
A defect in existing functionality

  
Type/Epic
Large body of work broken into multiple issues

  
Type/Feature
A new capability or user story

  
Type/Legendary
Major strategic pillar composed of multiple Epics

  
Type/Task
Technical or administrative work (not bug or feature)

  
Type/Testing
Test-only work item (TDD, test infrastructure, coverage)

No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aethyr/Aethyr!324
No description provided.