skills.rest
DuyITLOR
DuyITLORCOMMUNITY
Explore all skills by this author →
GitHub

Testing

Executes manual test cases against the EShop application and records results and bug reports.

Updated Jun 8, 2026
Search Tags:#qa#manual testing#bug report#regression#test cases#screenshot#eshop
One-click install
npx skills add https://github.com/DuyITLOR/group05_eshop --skill testing-duyitlor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Testing
Source: https://github.com/DuyITLOR/group05_eshop/tree/main/.agents/skills/Testing
Command: npx skills add https://github.com/DuyITLOR/group05_eshop --skill testing-duyitlor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually executing test cases, comparing actual behavior against the EShop specification, and documenting defects is repetitive and error-prone. This Skill walks through predefined test cases, updates actual results and pass/fail status, and produces structured bug reports with screenshots. ## Core Features & Use Cases - Test Case Execution: Runs test cases stored in ./tests/test-cases/<function> step by step in a browser against the running EShop app. - Result Tracking: Updates each test case file with the actual result and a Pass/Fail/Blocked status after execution. - Bug Reporting: Creates structured bug reports in ./bugs/<function> using a fixed template, with screenshots saved in an images subfolder. - Use Case: A QA student testing the FR01 registration function runs all its test cases, marks failures, and generates FR01-bug-01.md reports with embedded screenshots for each defect found. ## Quick Start Run the test cases for function FR01 against the EShop app, update their actual results and status, and create bug reports for any failures.

Frequently Asked Questions about Testing

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

FAQPage Schema
How do I run manual test cases for the EShop app?▼

Open the application URL in a browser, follow each test step in the test case files under ./tests/test-cases/<function>, and compare actual behavior with the expected results. Afterward, update each file with the actual result and a Pass, Fail, or Blocked status.

How do I write a bug report for a failed test case?▼

Create a Markdown file in ./bugs/<function> named <function>-bug-<sequence> using the provided bug report template. Include the bug description, covered test cases, preconditions, steps, expected and actual results, and embed a screenshot stored in the images subfolder.

What test statuses does this workflow support?▼

Each executed test case is marked with one of three statuses: Pass, Fail, or Blocked. The status is recorded directly in the test case file alongside the actual result observed during execution.

Where are bug screenshots stored?▼

Screenshots are saved in an images folder inside the corresponding function folder, for example ./bugs/FR01/images/FR01-bug-01.png. The bug report embeds the image using a relative path.

What documents are needed before testing a function?▼

You need the README.md for the functional specification and default test accounts, the api_specification.md for backend API behavior, and the setup_guide.md to run the application locally before executing any test cases.

Related Skills

Explore More Software Engineering Skills→
ssdeanxssdeanx
43

test-cases

Generate structured test cases with traceability from PRD requirements.

Community
Advanced
NealschNealsch

Forge-Defect-Management

Records, triages, tracks, and verifies defects through the software development lifecycle.

Community
Intermediate
FernanSuozaFernanSuoza

backend-development

Implement backend services with contract validation, authorization, and automated tests.

Community
Advanced
badhopebadhope

e2e-test

Automate end-to-end user flow testing across Playwright, Cypress, and Selenium.

Community
Advanced