tests

Define a testing strategy for GSE-One with traceability and evidence.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tjisousa/gensem --skill tests-tjisousa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tests
Source: https://github.com/tjisousa/gensem/tree/main/gse-one/plugin/skills/tests
Command: npx skills add https://github.com/tjisousa/gensem --skill tests-tjisousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines a complete testing strategy for GSE-One, enabling teams to plan, set up environments, write tests, run campaigns, and generate evidence that can be shared with stakeholders.

Core Features & Use Cases

  • Test strategy definition: Establish a formal testing pyramid, scope, and objectives for a sprint or project.
  • Environment setup: Outline prerequisites, tooling, and configurations needed to execute tests reliably.
  • Test authoring & execution: Create unit, integration, and end-to-end tests that verify requirements, design decisions, and policy constraints.
  • Campaign execution & evidence: Run campaigns across the SDLC and produce evidence packages for reporting and audit.
  • Traceability & reporting: Link tests to REQ/DES/DEC artefacts and generate clear, audit-ready results for stakeholders.

Quick Start

Trigger tests by issuing /gse:tests to load and execute the current sprint's testing plan.

Frequently Asked Questions about tests

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

FAQPage Schema
How do I define a complete test strategy for a sprint-based software project?

A test strategy establishes a formal testing pyramid, scope, and objectives for a sprint. It outlines environment setup, test authoring, campaign execution, and evidence generation to guide validation and verification across the software development lifecycle.

What is test traceability and how does it link tests to requirements?

Test traceability links executed tests to requirements, design, and decision artifacts. It ensures every test verifies a specific policy constraint or design decision, generating clear, audit-ready results for stakeholder reporting and compliance evidence.

How do I generate audit-ready evidence packages from test campaigns?

Generate evidence packages by running test campaigns across the SDLC and producing reports linked to REQ and design artifacts. This approach enforces test artifact versioning and prescribes evidence delivery for stakeholder reporting and audits.

Can I execute policy testing and verification across CI pipelines?

Yes, policy testing and verification apply across CI pipelines and development workflows. The strategy guides validation of policy constraints by specifying traceability to requirements and enforcing test artifact versioning within the pipeline.

What's the best way to structure unit, integration, and end-to-end tests for requirements verification?

Structure tests by authoring unit, integration, and end-to-end tests that verify requirements and design decisions. Establish a formal testing pyramid to scope objectives, then execute campaigns to produce evidence packages for reporting.