skills.rest
karloscodes
karloscodesCOMMUNITY
Explore all skills by this author →
Website𝕏@karloscodesGitHub

fusionaly-qa

Map code changes to unit, E2E, visual, and VM install test levels.

10|2|Updated Dec 17, 2025
Search Tags:#testing#e2e#qa#ci-cd#visual-qa#unit-tests
One-click install
npx skills add https://github.com/karloscodes/fusionaly-oss --skill fusionaly-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fusionaly-qa
Source: https://github.com/karloscodes/fusionaly-oss/tree/main/.claude/skills/fusionaly-qa
Command: npx skills add https://github.com/karloscodes/fusionaly-oss --skill fusionaly-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams plan and execute the appropriate level of QA (unit, E2E, visual, and VM/install tests) after code changes, ensuring quality without over-testing.

Core Features & Use Cases

  • Maps code changes (bug fixes, features, infra updates) to targeted test levels (Unit, E2E, Visual QA, VM install).
  • Provides recommended commands to run tests: make test, make test-e2e, make dev, and release checklists for production-readiness.
  • Supports end-to-end verification across development, testing, and deployment environments with clear criteria and guardrails.

Quick Start

Run unit tests after every change with make test, escalate to E2E with make test-e2e for feature changes, and use make dev for visual QA when UI verification is required.

Frequently Asked Questions about fusionaly-qa

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

FAQPage Schema
How do I determine the right level of QA testing for different code changes?▼

QA planning maps code changes like bug fixes, features, and infra updates to targeted test levels. It assigns unit tests for every change, E2E tests for features, and visual QA for UI updates to prevent over-testing.

What is the best way to automate E2E and visual QA verification workflows?▼

Automating E2E and visual QA workflows involves running targeted commands like make test-e2e for feature changes and make dev for visual UI verification, ensuring code changes meet clear development and deployment criteria.

When do I need to run VM install tests instead of unit tests?▼

VM install tests are needed for infrastructure changes, while unit tests run after every code change. Mapping change types to specific test levels ensures you execute the appropriate verification without over-testing.

How do I set up local development verification workflows for CI/CD pipelines?▼

Setting up local verification for CI/CD uses commands like make test for unit tests and make test-e2e for feature verification, documenting setup steps and release checklists to satisfy production-readiness guardrails.

Does this QA approach work for software projects with frequent code changes?▼

Yes, this approach targets software projects with frequent changes by escalating test levels based on change type, running unit tests for bug fixes and E2E tests for features to maintain quality efficiently.

Related Skills

Explore More Software Engineering Skills→
ByeongminLeeByeongminLee
2

test

Execute unit and integration tests guided by TEST_STRATEGY.md and TEST.md.

Community
Intermediate
hydrosolutionshydrosolutions
1

pre-deploy-validation

Validate tests, Docker builds, and GitHub Actions before production deployment.

Official
Intermediate
AcidicSoilAcidicSoil
1

test-design

Plan risk-informed test designs with acceptance criteria mapping and CI/CD integration.

Community
Advanced
Thanh-aperoThanh-apero
1

ck:test

Run unit, integration, e2e, and UI tests with QA reporting.

Community
Advanced