Plan: real screen/UI testing as a Ralph loop - #1
Draft
ThyFriendlyFox wants to merge 1 commit into
Draft
Conversation
Document real browser/screen verification as a persistent observe-act-evaluate-fix loop, with task schema, workspace artifacts, and phased implementation steps. Co-authored-by: ThyFriendlyFox <thyfriendlyfox@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a design plan for real screen/UI testing in ORC, structured as a Ralph loop (observe → act → evaluate → fix → repeat until acceptance criteria pass or budget is exhausted).
What’s in this PR
outline/screen-ui-testing-ralph-loop.mdScreenUIAgent(separate from unit-focusedTestAgent)ralph_ui_loopwith immutableacceptance[]outline/agent-types-needed.mdand README next stepsNot in this PR
Implementation of the agent itself — this is the plan only.