gate-4b-integration-tests

Validate integration test suites for no-hardcoding and credential handling.

6|Updated Feb 20, 2025
One-click install
npx skills add https://github.com/zerobias-org/module --skill gate-4b-integration-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate-4b-integration-tests
Source: https://github.com/zerobias-org/module/tree/main/.claude/skills/gate-4b-integration-tests
Command: npx skills add https://github.com/zerobias-org/module --skill gate-4b-integration-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates integration test suites against no-hardcoding requirements and proper credential handling.

Core Features & Use Cases

  • No hardcoding enforcement: Validates that tests obtain IDs and data from .env via Common.ts rather than hardcoded literals.
  • Structured test patterns: Verifies test files follow the expected describe/it patterns with multiple test cases per operation.
  • Credential-aware execution: Skips tests gracefully when credentials are unavailable and includes debug logging for traceability.
  • Common.ts integration: Ensures presence of a Common.ts exporting test data and helper functions like getConnectedInstance, hasCredentials, and getLogger.

Quick Start

Use gate-4b-integration-tests to verify your integration tests follow the no-hardcoding and environment-driven data patterns.

Frequently Asked Questions about gate-4b-integration-tests

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

FAQPage Schema
How do I stop hardcoding credentials and test data in TypeScript integration tests?

To stop hardcoding in integration tests, source credentials and test data from a .env file via a Common.ts module, using helper functions like getConnectedInstance and hasCredentials for environment-driven validation.

What is the proper way to handle missing credentials in end-to-end API testing?

Proper credential handling in API testing uses hasCredentials checks during test setup to gracefully skip test execution when credentials are unavailable, while still logging debug information for traceability.

How do I structure integration test suites for multiple test cases per operation?

Structure integration test suites using describe and it patterns to organize multiple test cases per operation, importing required test data and logger functions from a shared Common.ts file.

Why should integration tests avoid mocks and use environment variables instead?

Integration tests avoid mocks to validate real API client behavior, requiring environment variables from .env for credentials and data to ensure tests reflect actual end-to-end workflow conditions.

Can I use this validation gate for TypeScript projects without a Common.ts file?

No, this validation requires a Common.ts file that exports test data, getConnectedInstance, hasCredentials, and getLogger functions to properly enforce no-hardcoding and logging standards across test files.

What logging standards are required for integration test files?

Integration test files require mandatory logger usage imported from Common.ts to ensure debug logging and traceability across all test cases, replacing hardcoded values with environment-driven data.