dehaze-sdk-js-test

Automate standardized Vitest API integration testing workflows for dehaze-sdk-js.

2|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/earthy-zinc/dehaze-system --skill dehaze-sdk-js-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dehaze-sdk-js-test
Source: https://github.com/earthy-zinc/dehaze-system/tree/main/.codebuddy/skills/dehaze-sdk-js-test
Command: npx skills add https://github.com/earthy-zinc/dehaze-system --skill dehaze-sdk-js-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized workflow for writing, running, and diagnosing Vitest API integration tests for the dehaze-sdk-js project, reducing ambiguity and speeding up debugging when tests fail.

Core Features & Use Cases

  • Standardized test skeletons and conventions for dehaze-sdk-js Vitest API tests.
  • Failure-attribution workflow including curl verification, SDK coverage checks, OAS alignment, and backend data validation.
  • Clear guidance for typical test scenarios: creating test data, asserting responses, and isolating flaky tests.

Quick Start

Run the standardized Vitest API tests for dehaze-sdk-js using the test suite and follow the failure-analysis workflow.

Frequently Asked Questions about dehaze-sdk-js-test

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

FAQPage Schema
How do I debug failing Vitest API integration tests for a JavaScript SDK?

A standardized Vitest API testing workflow debugs failing JavaScript SDK tests by applying curl verification, SDK wrapper coverage checks, OpenAPI Specification alignment, and backend data validation to isolate the root cause.

What is the best way to structure deterministic Vitest API tests for JavaScript?

Standardized test skeletons enforce deterministic Vitest API test structure and setup for JavaScript SDKs, ensuring consistent test data creation, response assertions, and isolation of flaky tests.

Why does my Vitest API test fail and how do I attribute the failure to the backend?

Attribute Vitest API test failures by executing curl verification to check raw endpoints, validating OpenAPI Specification alignment, and performing backend data checks to confirm database state.

Can I use Vitest to isolate flaky API integration tests in a JavaScript SDK workflow?

Yes, you can isolate flaky API integration tests in a Vitest workflow by following standardized failure-analysis guidance that separates deterministic test setup from external API instability and backend data checks.