skills.rest
Hakkadaikon
HakkadaikonCOMMUNITY
Explore all skills by this author →
𝕏@hakkadaikonGitHub

nonfunctional-attributes

Guides quality-assurance nonfunctional testing covering security, accessibility, compatibility, and contract verification.

Updated Jun 24, 2026
Search Tags:#accessibility#security testing#wcag#contract testing#pact#iso 25010#nonfunctional testing
One-click install
npx skills add https://github.com/Hakkadaikon/hymme --skill nonfunctional-attributes-hakkadaikon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nonfunctional-attributes
Source: https://github.com/Hakkadaikon/hymme/tree/main/skills/nonfunctional-attributes
Command: npx skills add https://github.com/Hakkadaikon/hymme --skill nonfunctional-attributes-hakkadaikon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often run nonfunctional tests ad hoc without clear pass/fail thresholds, leaving security vulnerabilities, accessibility violations, and API compatibility breaks undetected until production. This Skill defines how to verify quality attributes as satisfied properties (zero violations, no contract breakage) rather than vague coverage percentages. ## Core Features & Use Cases - Quality-attribute catalog: Covers security testing, penetration testing, DAST/SAST/IAST, SCA dependency scanning, usability, accessibility (a11y/WCAG), cross-browser compatibility, i18n/l10n, reliability (MTBF), failover, chaos engineering, recovery, and contract testing mapped to ISO/IEC 25010. - Accessibility execution workflow: Step-by-step procedure to enumerate page states, run automated axe-core scans asserting zero violations, and manually cover keyboard navigation and contrast checks that automation misses. - Consumer-driven contract testing: Operational guidance for Pact-based verification, including fixing core fields with concrete values, wiring provider-side CI verification, and managing version compatibility via a pact broker. - Use Case: After the test-catalog router assigns accessibility testing to a behavior, use this Skill to set up @axe-core/playwright scans across modal, error, and logged-in states with a CI gate that fails on any new WCAG violation. ## Quick Start Ask the AI to apply the nonfunctional-attributes skill to set up accessibility testing with axe-core and a consumer-driven contract test with Pact for your service boundary.

Frequently Asked Questions about nonfunctional-attributes

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

FAQPage Schema
How do I set up accessibility testing with axe-core and Playwright?▼

Use @axe-core/playwright to scan each major page state, including modals, error states, and logged-in views, then assert that the violations array is empty. Choose a WCAG conformance level such as AA via withTags, and fail CI on any new violation.

How does consumer-driven contract testing with Pact work?▼

The consumer declares the exact response fields it depends on as a pact file, and the provider's CI verifies that pact without running the consumer. Register contracts in a pact broker and use can-i-deploy to confirm compatibility across all deployed version combinations.

What is the difference between DAST, SAST, and IAST security testing?▼

DAST probes a running application externally, SAST analyzes source code statically, and IAST instruments the application at runtime. Layering all three reduces missed vulnerabilities because each detects a different class of issues.

Can automated tools fully verify WCAG accessibility compliance?▼

No. Automated scans like axe-core catch mechanical violations, but keyboard-only navigation, focus order, screen reader output, and color-independent information require manual checks. Use automation to fix the regression floor and a manual checklist for the rest.

When should I not use contract testing?▼

Skip contract testing for calls within a single process or for stable APIs that rarely change, since the pact infrastructure is overkill there. It pays off when independently deployed teams or microservices risk breaking backward compatibility.

Related Skills

Explore More Software Engineering Skills→
BedaBeda-GrowthBedaBeda-Growth

Closeout Plan

Generates prioritized, executable production-closeout plans from pipeline snapshots and skill catalogs.

Official
Advanced
nesquikmnesquikm
6

debug

Diagnose and resolve failing tests and gate checks through structured debugging phases.

Community
Advanced
Omar-ObandoOmar-Obando
44

load-testing

Design and run load tests with k6, JMeter, Locust, or Gatling.

Community
Intermediate
nicholls-incnicholls-inc
5

lean-spec

Convert signed-off informal verification specs into type-checked Lean 4 stubs.

Official
Advanced