Cobalt — Testing

Name: Cobalt — Testing
Availability: InStock
Author: Cobalt

Standardize unit and integration testing protocols within the Cobalt monorepo.

7|Updated Mar 15, 2026

Search Tags:#workflow #vitest #testing #integration #drizzle #cobalt

Ready to run

npx skills add https://github.com/Cobalt-Money/Cobalt --skill cobalt-testing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Cobalt — Testing
Source: https://github.com/Cobalt-Money/Cobalt/tree/main/.agents/skills/cobalt/testing
Command: npx skills add https://github.com/Cobalt-Money/Cobalt --skill cobalt-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a unified framework for managing unit and integration tests, ensuring consistent test execution, proper mocking strategies, and reliable database schema validation within the Cobalt monorepo.

Core Features & Use Cases

Unit Testing Strategy: Defines conventions for co-located tests and system-boundary mocking to ensure fast, reliable feedback loops.
Integration Harness: Provides a server-based testing approach using Nitro and Docker-hosted PostgreSQL to verify end-to-end workflows without polluting production data.
Regression Protection: Implements DB-shape validation using Drizzle-Zod to catch schema drift before it reaches production.

Quick Start

Use the Cobalt Testing skill to configure the integration test harness and run the full suite of sad-path tests against the local development server.

Frequently Asked Questions about Cobalt — Testing

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

FAQPage Schema

How do I set up integration testing with Vitest and Docker-hosted PostgreSQL?▼

Integration testing with Vitest and PostgreSQL uses a Nitro server-based harness to execute end-to-end workflow verification against a Docker-hosted database, isolating tests from production data. It standardizes execution within the Cobalt monorepo.

What is the best way to prevent database schema drift in a monorepo?▼

Preventing database schema drift relies on DB-shape validation using Drizzle-Zod to enforce strict schema boundaries. This catches regressions in financial data processing before they reach production environments.

How does system-boundary mocking improve unit testing reliability?▼

System-boundary mocking improves unit testing by enforcing strict isolation at architectural edges. Co-located tests define conventions that ensure fast feedback loops without cascading failures from external dependencies.

Can I run sad-path tests against a local development server for workflow verification?▼

Yes, you can run sad-path tests against a local development server. The integration harness is configured to execute the full suite of sad-path tests, verifying workflow reliability without polluting production data.

Does the testing harness require Nitro to execute server-based integration tests?▼

Yes, Nitro is required to facilitate the execution of server-based integration tests. It works alongside Docker-hosted PostgreSQL to verify end-to-end workflows within the standardized testing harness.

Why should I standardize testing protocols for financial data processing?▼

Standardizing testing protocols for financial data processing prevents regressions by enforcing consistent execution and strict database schema validation. It ensures reliable unit and integration verification across the monorepo.