test-data

Generate deterministic billing test data with SQL across Cottage database tables.

Updated Aug 23, 2026

Search Tags:#automation #subscriptions #supabase #playwright #billing #test-data #electric-bill

Ready to run

npx skills add https://github.com/Cottage-Energy/cottage-tests --skill test-data-cottage-energy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-data
Source: https://github.com/Cottage-Energy/cottage-tests/tree/main/.claude/skills/test-data
Command: npx skills add https://github.com/Cottage-Energy/cottage-tests --skill test-data-cottage-energy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides utilities to create and manage test data for billing users, subscriptions, bills, and account states in the Cottage system, enabling deterministic test scenarios.

Core Features & Use Cases

Test data recipes for billing user creation, active account setup, processed bills, subscriptions, connect-ready users, multi-property users, flags manipulation, and overdue/bill reminder scenarios.
DB-backed setup using SQL operations across ElectricAccount, CottageUsers, ElectricBill, Subscription, and related tables to create realistic test states.
Reusable planning with pre-flight checks and structured data sets to validate gating and eligibility gates before test execution.

Quick Start

Request a ready-to-run test data set for a billing user with processed bills and an active account.

Frequently Asked Questions about test-data

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

FAQPage Schema

How do I generate deterministic test data for billing users and subscriptions?▼

Yes, you can set up negative test data scenarios by manipulating flags and creating overdue bill states using scripted SQL operations across ElectricBill and related tables to simulate edge cases.

What's the best way to set up test data for overdue bills and dead-flag account states?▼

The best way to set up overdue bill and dead-flag states is through structured SQL data recipes that insert specific account conditions into ElectricAccount and ElectricBill tables with validated pre-flight checks.

Does this test data approach work with Supabase and automated Playwright workflows?▼

Pre-flight checks validate gating and eligibility conditions before test execution, ensuring the generated data sets for billing users, subscriptions, and account states are accurate and reproducible.

Can I create multi-property user test data with processed electric bills?▼

This approach handles positive, negative, and dead-flag data scenarios across multiple related tables, ensuring comprehensive coverage of billing and account states for deterministic testing environments.

What limitations exist when managing subscription and billing test data through SQL scripts?▼

Limitations include dependency on DB-backed SQL workflows and the need for pre-flight checks; complex multi-table relationships like ElectricAccount and Subscription require careful scripted coordination to maintain data consistency.