web-gui-tester

Featured

Verify web frontend behavior through real GUI interactions, read-only page inspection, and screenshots. Use for frontend acceptance tests, bug reproduction, interaction feedback, and visual checks with the browser tools available in the session.

Web & Frontend 2,629 stars 229 forks Updated today LGPL-3.0

Install

View on GitHub

Quality Score: 90/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- Adapted for codexhost from ZCode 872ad960de7ec172591f7e1952f7849229f94521. See ../NOTICE.md for provenance and licenses. --> ## codexhost browser runtime Use [control-browser](../control-browser/SKILL.md) to select an actually available browser tool and obey its documentation. This skill provides test methodology and does not install ZCode's browser runtime. Reuse prior user authorization and approved test scope; request missing credentials or a genuinely unapproved external effect only when needed. Treat example tool names below as conditional on the current session. ## Core Principles 1. **Pure GUI black-box testing**: Interact only with elements that are visible and operable on the page, simulating real user behavior. During verification, screenshots and/or read-only DOM inspection are allowed, but injecting JavaScript to modify page state, trigger interactions, or bypass frontend logic is strictly prohibited. 2. **Faithful to the actual page**: All conclusions must be based on the page’s actual behavior. Do not guess or speculate. If a normal GUI operation fails, stop and report it; do not use alternative methods to force progress. 3. **Separate testing from fixing**: Do not modify the code under test during testing. If a bug blocks the current path, record the issue, skip that path, and continue testing other unaffected points. Only begin fixing bugs after testing is explicitly declared complete and the user has explicitly or implicitly requested code changes. 4...

Details

Author
BytePioneer-AI
Repository
BytePioneer-AI/codex-host
Created
2 months ago
Last Updated
today
Language
TypeScript
License
LGPL-3.0

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Featured

control-browser

Control a browser using the tools available in the current session to navigate, inspect, click, fill, capture and verify pages. Use for browser actions; combine with web-gui-tester for structured GUI testing.

2,629 Updated today
BytePioneer-AI
AI & Automation Listed

web-test

Verify UI behaviour in a real browser — derive the scope from a task's acceptance criteria and/or the uncommitted diff, resolve the target environment and its auth state, drive the page through a browser-automation MCP (Claude in Chrome), exercise the happy path plus a required set of edge cases, capture console/network/visual evidence, write `{ID} web-test-summary.md` (executed test plan + reproducible bug reports) into the task folder, and record a WEBTEST verdict in the task log. Used by the Tester (and standalone on work-in-progress). Interactive sessions only — a headless orchestrated run must not drive a browser (each call stalls it on a governance approval card). Mutating a shared environment is HIGH; production is CRITICAL.

3 Updated 4 days ago
bibennurbani
Web & Frontend Listed

browser-testing

Tests a real web user flow with a browser by asserting semantic behavior, network and loading states, keyboard access, responsive layouts, and stable visual evidence. Use for browser bugs, end-to-end UI behavior, responsive or accessibility checks, and screenshot baselines. Not for static source review without a browser or for backend-only tests.

95 Updated 1 months ago
thiientv