backend-datasets

Create and load Drumr backend datasets in JSONL format.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/slingr-stack/qa-test-drumr --skill backend-datasets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-datasets
Source: https://github.com/slingr-stack/qa-test-drumr/tree/main/project-management-app/.agents/skills/backend-datasets
Command: npx skills add https://github.com/slingr-stack/qa-test-drumr --skill backend-datasets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork and inconsistency from creating, validating, and loading Drumr backend datasets, so teams can seed data and test scenarios reliably.

Core Features & Use Cases

  • Dataset Authoring: Create one JSONL file per model in the required backend/src/dataSets/<idDataSource>/<dataset-name>/ structure.
  • Dataset Loading: Load datasets through the Drumr CLI with the right datasource, dataset name, and optional model filters.
  • Validation and Recovery: Check references, file fixtures, include or exclude filters, and troubleshooting steps when loading fails.
  • Use Case: A developer preparing integration tests can generate a realistic seed dataset, load only selected models, and verify file-backed records with relative paths.

Quick Start

Ask the assistant to create or update a backend dataset in the correct Drumr folder and load it with the right datasource and model filters.

Frequently Asked Questions about backend-datasets

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

FAQPage Schema
How do I create backend datasets in JSONL format for integration testing?

To create backend datasets, generate one JSONL file per model in the required backend/src/dataSets/<idDataSource>/<dataset-name>/ folder structure. Each file defines records for a specific model, enabling reliable data seeding and test fixture preparation.

What is the best way to load test fixtures through a backend CLI?

Loading test fixtures through the backend CLI requires specifying the correct datasource, dataset name, and optional include or exclude model filters. This ensures only selected models are loaded, streamlining integration test preparation.

Why does my backend dataset loading fail when referencing file fixtures?

Dataset loading fails when references are invalid or file fixture paths are incorrect. Ensure all references point to valid records and file-backed records use correct relative paths within the datasource folder structure to prevent loading errors.

Can I load only specific models from a JSONL dataset?

Yes, you can load only specific models from a JSONL dataset by applying safe include or exclude model filters during the CLI loading process. This allows targeted seeding without loading the entire dataset.

When do I need JSONL dataset files for backend seeding?

JSONL dataset files are needed for backend seeding when preparing model-specific test scenarios or integration tests. They provide structured, line-delimited records that validate references and ensure reliable data loading through the CLI.

Do I need a specific folder structure to validate backend dataset references?

Yes, validating backend dataset references requires the correct datasource folder structure under backend/src/dataSets/<idDataSource>/<dataset-name>/. Proper structure ensures references, file fixtures, and model filters are recognized during CLI loading.