dora-testing

Run unit, integration, and live database tests for the Dora workbench.

14|1|Updated May 11, 2025
One-click install
npx skills add https://github.com/remcostoeten/dora --skill dora-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dora-testing
Source: https://github.com/remcostoeten/dora/tree/main/.claude/skills/dora-testing
Command: npx skills add https://github.com/remcostoeten/dora --skill dora-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured framework for verifying changes to the Dora database workbench, ensuring that new features or bug fixes do not introduce regressions across the complex stack of TypeScript, Rust, and live database integrations.

Core Features & Use Cases

  • Multi-Layer Verification: Orchestrates testing across pure functions, React components, Rust service logic, and live database adapters.
  • CI Gate Management: Defines the specific commands required to validate changes before they are merged, including feature-gated Rust tests and browser boot smoke tests.
  • Use Case: When modifying the SQL query builder, use this skill to determine whether to run unit tests for the parser or to trigger the live MySQL/MariaDB integration suite to ensure the generated SQL executes correctly against a real database.

Quick Start

Use the dora-testing skill to identify the correct test commands for verifying a change to the DuckDB engine integration.

Frequently Asked Questions about dora-testing

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

FAQPage Schema
How do I run database tests across TypeScript and Rust layers simultaneously?

Verify database integration changes by executing live database tests that validate generated SQL against real MySQL or MariaDB instances. This ensures query builders execute correctly against live database adapters without introducing regressions.

How do I verify DuckDB engine integration changes without breaking existing functionality?

Prevent regressions when modifying the SQL query builder by running targeted parser unit tests. For broader validation, trigger the live MySQL and MariaDB integration suite to ensure generated SQL executes correctly against a real database.

Does Vitest work with Rust service logic for live database integration testing?

Yes, browser boot smoke tests are required as a CI gate before merging changes. They validate the frontend TypeScript and React components, ensuring the application boots correctly and preventing regressions in the user interface.

What is the best way to prevent regressions when modifying a SQL query builder in a full-stack application?

CI gate configurations define the specific test commands required to validate changes before merging. They include feature-gated Rust tests and browser boot smoke tests to ensure functional integrity and prevent regressions across the stack.

Why does my CI gate fail when testing database workbench changes across different environments?

Feature-gated Rust tests are used to validate specific Rust service logic and database engine integrations like DuckDB. They ensure that conditional code paths execute correctly without running unnecessary tests during standard CI gate validation.