test-authoring

Plan and author focused tests for Swift projects and CI pipelines.

26|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/TeamSloppy/Sloppy --skill test-authoring-teamsloppy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-authoring
Source: https://github.com/TeamSloppy/Sloppy/tree/main/Sources/sloppy/Resources/Skills/test-authoring
Command: npx skills add https://github.com/TeamSloppy/Sloppy --skill test-authoring-teamsloppy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and maintaining reliable tests for software features can be error-prone and time-consuming; this skill guides you to plan, write, and validate unit, integration, regression, and acceptance tests with clarity and repeatability.

Core Features & Use Cases

  • Test planning: Define what to test, select the appropriate level (unit, integration, regression, acceptance), and identify required fixtures.
  • Authoring guidance: Provide structured test templates, naming conventions, and validation commands to ensure deterministic results.
  • Use Case: Convert a feature requirement into a test scaffold that covers behavior, edge cases, and rollback scenarios.

Quick Start

Plan the test strategy for a feature and generate a focused unit/integration/acceptance test scaffold with validation steps.

Frequently Asked Questions about test-authoring

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

FAQPage Schema
How do I write unit and integration tests that produce deterministic validation results?

To plan focused tests, first define the specific behavior to validate, then select the appropriate testing level such as unit, integration, regression, or acceptance. Finally, identify required fixtures and document the validation steps aligned with project conventions.

Does this test authoring approach support Swift projects and CI pipelines?

Test planning and authoring guides the creation of structured test scaffolds that cover behavior, edge cases, and rollback scenarios. It implements clear naming conventions and structured documentation to ensure repeatability across unit and integration tests.

What is the best way to convert a feature requirement into an acceptance test scaffold?

The test planning process covers four levels: unit testing for individual components, integration testing for interactions, regression testing to prevent backwards compatibility issues, and acceptance testing to validate feature requirements against expected behavior.

When should I use regression tests versus acceptance tests in my QA workflow?

Use regression tests to verify that recent changes have not adversely affected existing functionality, and apply acceptance tests to confirm that a feature meets its defined business requirements and behavior expectations within your QA workflow.