agentleFS
fatihkanfatihkan/badi/.claude/skills-vault/testing/SKILL.md

testing

Skill8 starsChanged 3 months agoMITView on GitHub

Software test strategy, test automation, performance testing, security testing, and quality assurance skills. Jest, Pytest, Playwright, Cypress, k6, security regression. Triggers on: testing, test automation, Jest, Playwright, Cypress, performance test, load test, QA, regression test, test strategy.

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use bundle-dependency-prs, update-library-template and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    bundle-dependency-prs

    Fix broken dependency update PRs and aggregate the ones that work into one PR.

    Also in 7 projects that use this

  • MicrosoftSkill

    update-library-template

    Merges the latest Library.Template into this repo (at position of HEAD) and resolves conflicts.

    Also in 7 projects that use this

  • zetaloopSkill

    assign-copilot

    Assigns a GitHub issue to the Copilot coding agent, optionally specifying a custom agent. Use this when asked to assign an issue to Copilot or delegate an issue to CCA.

    Also in 3 projects that use this

  • NVIDIA-NeMoSkill

    build-and-dependency

    Dev environment setup for Megatron Bridge — container-based development, uv package management, lockfile regeneration, adding dependencies, Slurm container usage, and common build pitfalls.

    Also in 3 projects that use this

  • timmo001Skill

    changeset-scope

    Keep all scoped code work contained to the user-defined changeset. Use for implementation, fixes, diagnosis, refactoring, cleanup, and review when explicit instructions, named files, diffs, branches, pull requests, or injected work scopes define the boundary.

    Also in 3 projects that use this

  • JetBrainsSkill

    module-dependencies

    Add or modify IntelliJ module dependencies in `.iml` files.

    Also in 3 projects that use this

The file

Files
SKILL.md

Testing Skills

This file contains all the skills across software test strategy, test automation, performance testing, security testing, and quality assurance.


test-strategy-design

Sets quality goals and the test approach by building the project's comprehensive test strategy.


unit-test-writing

Raises code quality with effective unit-test writing techniques and best practices.


integration-testing

Verifies compatibility by testing the integration points between components.


end-to-end-testing

Validates business flows by testing the application end to end from the user's perspective.


test-automation-framework

Builds a repeatable, sustainable test process by designing the test automation infrastructure.


tdd-practice

Raises code quality by applying the Test Driven Development methodology to the project.


bdd-scenarios

Converts business requirements into test scenarios with Behavior Driven Development.


api-testing

Tests API endpoints for functionality, performance, and security.


performance-test-plan

Builds and runs the comprehensive plan measuring application performance.


load-test-design

Determines system capacity limits by designing load-test scenarios.


stress-test-planning

Tests the system's behavior at boundary conditions and its recovery capacity with stress tests.


security-testing

Detects vulnerabilities by planning application security tests.


mobile-test-strategy

Builds the comprehensive test strategy and automation plan for mobile applications.


regression-test-suite

Verifies changes do not break existing functionality by building a regression suite.


test-data-management

Develops the strategy for creating, masking, and managing test data.


test-environment-management

Develops the strategy for efficiently managing, provisioning, and maintaining test environments.


exploratory-testing

Discovers bugs that structured tests would miss, using exploratory testing techniques.


accessibility-testing

Tests the application's compliance with accessibility standards (WCAG).


visual-regression-testing

Automatically verifies UI changes do not break visual consistency.


test-coverage-analysis

Evaluates test sufficiency and finds the gaps through code-coverage analysis.


bug-reporting

Speeds up resolution by building effective bug-reporting standards and process.


test-management-tool

Raises test-process efficiency by configuring the test management tool.


mutation-testing

Evaluates the test suite's fault-catching capacity with mutation testing.


contract-testing

Prevents integration mismatches by testing inter-service API contracts.


chaos-testing

Tests the application's behavior under unexpected conditions with chaos testing.


usability-test-plan

Builds the usability test plan for evaluating the user experience.


cross-browser-testing

Builds the test strategy verifying consistent behavior across browsers.


database-testing

Tests the correctness, integrity, and performance of database operations.


test-pipeline-integration

Builds continuous-testing infrastructure by integrating automation into the CI/CD pipeline.


test-metric-reporting

Builds the system that tracks and reports test-process metrics.


test-design-techniques

Builds effective test scenarios with systematic test-design techniques.


smoke-test-suite

Builds the smoke-test suite that quickly verifies core functionality.


acceptance-testing

Designs the user acceptance testing process verifying business requirements are met.


test-automation-strategy

Plans the test automation pyramid and automation scope strategically.


continuous-testing

Speeds up quality feedback by integrating continuous-testing practices into development.


test-quality-metrics

Applies metrics and analyses that evaluate the quality of the test suite itself.


shift-left-testing

Enables early defect detection by moving test activities to the start of development.


test-data-factory

Provides consistent, rich data for scenarios by building a test-data factory.


test-documentation

Builds structures that document test processes, scenarios, and results effectively.


test-containerization

Builds repeatable test infrastructure by standardizing environments with containers.


property-based-testing

Discovers edge cases traditional scenarios would miss, via property-based testing.


test-reporting

Builds the reporting system that visualizes results effectively for stakeholders.


risk-based-testing

Tests the most critical areas first through risk-based test prioritization.


test-team-management

Builds the test team's organization, competence development, and efficiency strategy.


test-process-improvement

Applies efficiency and effectiveness improvements by analyzing current test processes.


test-tool-evaluation

Picks the best fit for the project by evaluating test tools and frameworks.


test-environment-isolation

Delivers reliable results by isolating test environments from each other.


snapshot-testing

Automatically detects unexpected changes by recording output snapshots.


load-test-scenarios

Designs and runs detailed test scenarios for different load patterns.


test-automation-maintenance

Applies the strategy keeping existing automation code maintainable and stable.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.