scaffold-test

Scaffold .NET integration tests for API endpoints with SSE event verification.

15|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/aalmada/BookStore --skill scaffold-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scaffold-test
Source: https://github.com/aalmada/BookStore/tree/main/.claude/skills/scaffold-test
Command: npx skills add https://github.com/aalmada/BookStore --skill scaffold-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of integration tests for API endpoints, focusing on SSE event verification and TUnit-based patterns to ensure end-to-end behavior is validated in automated pipelines.

Core Features & Use Cases

  • Scaffolds tests in tests/BookStore.AppHost.Tests with consistent naming and structure.
  • Verifies SSE events after mutations to confirm correct notifications.
  • Provides reusable TestHelpers utilities to generate authenticated clients and common test actions.
  • Supports typical CRUD and query endpoints across admin and public surfaces.

Quick Start

Use this skill when starting integration tests for a new endpoint. Create a test file in tests/BookStore.AppHost.Tests with a {Feature}Tests.cs class, implement tests following the templates, and run the test runners (e.g., /run-integration-tests or dotnet test) to verify SSE events.

Frequently Asked Questions about scaffold-test

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

FAQPage Schema
How do I automate integration testing for API endpoints with SSE event verification in ASP.NET Core?

Automate SSE event verification in integration tests by scaffolding TUnit test classes. This validates that create, update, delete, and query API flows correctly emit Server-Sent Events notifications using TestHelpers utilities for authenticated HTTP calls.

What is the best way to verify SSE notifications after CRUD mutations in C# integration tests?

Verify SSE notifications after CRUD mutations by applying TUnit test patterns and TestHelpers utilities. This ensures correct Server-Sent Events are emitted and validated automatically in your pipelines after data mutations occur.

Do I need TUnit.Core and TestHelpers to run authenticated HTTP calls and verify SSE events?

Yes, you need TUnit.Core and TestHelpers utilities within a .NET test project. These dependencies are required to generate authenticated clients, execute HTTP calls, and verify SSE events during integration testing workflows.

How do I scaffold integration tests for a new API endpoint using TUnit?

Scaffold integration tests by creating a {Feature}Tests.cs class in your test project, implementing tests using TUnit templates, and running the test runner. This automates SSE event verification for new API endpoints.

Can I use this integration testing approach for both admin and public API surfaces?

Yes, this integration testing approach supports typical CRUD and query endpoints across both admin and public API surfaces. It ensures SSE events are emitted and validated consistently regardless of the API surface tested.