browser-testing
Verify UI behavior using browser automation, visual checks, and DevTools-style inspection. Use for end-to-end flows, visual regressions, accessibility in the browser, or when unit tests are insufficient for user-facing behavior.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- browser-testing
- description
- Verify UI behavior using browser automation, visual checks, and DevTools-style inspection. Use for end-to-end flows, visual regressions, accessibility in the browser, or when unit tests are insufficient for user-facing behavior.
03 SKILL.md 正文
Browser Testing
Overview
Some behaviors can only be confidently verified in a real browser. Use browser testing selectively for high-value user flows and visual/accessibility checks.
When to Use
- Critical user journeys (login, checkout, core workflows)
- Visual or layout regressions
- Accessibility validation in a real browser
- Debugging frontend issues that only appear at runtime
Core Practices
- Prefer stable selectors (roles, labels, test ids) over brittle CSS/XPath
- Keep E2E tests focused and relatively few — they are slower and more fragile
- Combine with component and unit tests for speed
- Capture screenshots or traces on failure for easier debugging
- Run against realistic data and viewports when relevant
Verification
- Critical paths have automated browser coverage or a clear manual test script
- Failures produce actionable artifacts (screenshots, traces, logs)
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.