Automate end-to-end QA testing and iterative bug remediation for web applications.
npx skills add https://github.com/cegit27/moodle-proctor --skill qa-cegit27
Please help me install this Agent Skill. Skill: qa Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/qa Command: npx skills add https://github.com/cegit27/moodle-proctor --skill qa-cegit27
Manual QA testing is inconsistent, misses edge cases, and breaks developer flow with repetitive bug-hunt cycles. This skill automates the entire QA-to-fix pipeline so teams can ship with confidence instead of manually checking every interaction.
Use the qa skill to test the deployed web application and automatically fix any bugs found.
High-intent search queries and answers about installing and using this skill.
Automated QA testing for web applications uses browser automation to validate user interfaces, functional workflows, performance metrics, and accessibility standards. It systematically checks critical, high, medium, and low severity tiers to ensure ship-readiness.
Yes, you can generate a QA report without applying fixes by using a report-only mode. This evaluates your web application, produces health scores, and outputs a ship-readiness summary while leaving your source code untouched.
Automated bug fixing iteratively patches source code and commits each fix atomically to version control. After applying a fix, it re-verifies the functionality to ensure the bug is resolved before moving to the next issue.
Quick testing covers critical and high severity issues, Standard adds medium severity coverage, and Exhaustive includes cosmetic checks. Choose a tier based on your timeline to balance validation depth with delivery speed.
Yes, browser automation capabilities are required to execute end-to-end quality assurance testing. This allows the system to interact with user interfaces and validate functional workflows across your web application.
The best way to validate ship-readiness is through exhaustive automated QA testing that checks UI, workflows, performance, and accessibility. This produces before and after health scores alongside a structured ship-readiness summary.
apollostreetcompanyAutomate browser navigation, form interaction, screenshots, and data scraping via CDP.
putrawitamaRun tiered QA tests on web applications and document fixed bugs.
mahg-esDesign and enforce CI/CD quality gates for code, tests, security, build, E2E, and performance.
JaronTamEnumerate branching paths to detect unhandled edge cases in code, specs, or diffs.
