GUI Testing

Generates GUI test checklists, records results, and produces individual bug report files.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/DuyITLOR/group05_eshop --skill gui-testing-duyitlor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: GUI Testing
Source: https://github.com/DuyITLOR/group05_eshop/tree/main/.agents/skills/GUI%20Testing
Command: npx skills add https://github.com/DuyITLOR/group05_eshop --skill gui-testing-duyitlor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual GUI testing often lacks structure: testers skip checklist items, lose track of pass/fail results, and write inconsistent bug reports. This Skill standardizes the entire GUI testing workflow so every UI check is documented and every failure becomes a traceable bug report. ## Core Features & Use Cases - Standardized GUI Checklists: Creates a Markdown checklist from a template covering four categories (IA01 General UI standards, IA02 Forms, IA03 Navigation, IA04 Feedback/State) with environment details and a test summary table. - Result Recording via Code Inspection or Live Testing: Fills in Passed/Failed results with notes by inspecting UI source code (e.g., JSX, HTML tags, CSS classes) or by testing the running application. - Per-Bug Report Files: For every Failed test case, generates a separate bug report file (named by test case ID) with description, steps, expected/actual results, Severity, Priority, and screenshot placeholder. - Use Case: Testing an EShop shopping cart page against a requirements spec — the Skill produces a 16-item checklist with a summary (4 passed, 12 failed) and individual bug reports like GUI-CART-001.md for each failure. ## Quick Start Ask the AI to perform GUI testing on a specific page or component, for example: run GUI testing on the shopping cart page against the system requirements specification.

Frequently Asked Questions about GUI Testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GUI testing checklist for a web page?▼

Use the provided checklist template covering four categories: general UI standards, forms, navigation, and feedback/state. Each item gets an ID, expected result, pass/fail status, and notes, plus an environment table and test summary.

How to write a bug report for a failed UI test case?▼

Create one separate Markdown file per failed test case, named after its test case ID. Include bug description, preconditions, test steps, expected and actual results, severity (Minor/Major/Critical), priority (Low/Medium/High), and a screenshot reference.

Can GUI testing be done by inspecting source code instead of running the app?▼

Yes, the workflow supports code inspection of UI source files such as JSX or HTML. You can verify heading tags, CSS color classes, and static text directly in the code, or alternatively test the live running application in a browser.

What severity and priority levels should UI bugs use?▼

Severity is rated Minor, Major, or Critical based on how badly the UI deviates from the specification. Priority is rated Low, Medium, or High based on how urgently the bug should be fixed.

What are the limitations of manual GUI checklist testing?▼

Manual checklist testing depends on the tester's judgment and does not scale to large regression suites. It verifies visual and structural compliance but does not cover functional logic, performance, or automated cross-browser rendering differences.