long-task-st

Name: long-task-st
Availability: InStock
Author: suriyel

Verify integrated system behavior and non-functional requirements before release.

178|43|Updated Feb 12, 2026

Search Tags:#quality assurance #integration testing #e2e testing #system testing #release readiness #nfr verification

Ready to run

npx skills add https://github.com/suriyel/longtaskforagent --skill long-task-st

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: long-task-st
Source: https://github.com/suriyel/longtaskforagent/tree/main/skills/long-task-st
Command: npx skills add https://github.com/suriyel/longtaskforagent --skill long-task-st

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures the entire software system is robust, reliable, and meets all requirements by performing thorough cross-feature and system-wide verification after all individual features have passed their tests.

Core Features & Use Cases

System-wide Verification: Executes tests that cover interactions between features, end-to-end workflows, and non-functional requirements (performance, security, etc.).
Quality Gate Enforcement: Acts as a critical gate before release, ensuring the integrated system is production-ready.
Use Case: After all features of a web application are developed and individually tested, this Skill runs scenarios like a full user registration-to-purchase flow, checks overall system performance under load, and verifies security compliance across the entire application.

Quick Start

Run comprehensive system testing for the project.

Frequently Asked Questions about long-task-st

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

FAQPage Schema

How do I perform system testing to verify release readiness for an integrated application?▼

System testing for release readiness involves executing cross-feature and end-to-end workflows to validate integrated system behavior and non-functional requirements against SRS specifications. This Skill enforces quality gates by requiring evidence-based regression, performance, and security testing results.

What is the difference between integration testing and end-to-end system testing?▼

Integration testing verifies interactions between specific modules, while end-to-end system testing validates complete user workflows across the entire integrated system. This Skill performs both alongside regression and exploratory testing to ensure overall system quality before release.

How do I verify non-functional requirements like performance and security before a release?▼

Verifying non-functional requirements requires executing dedicated performance and security testing across the fully integrated system. This Skill validates NFRs alongside functional end-to-end workflows, ensuring all quality gates are met with evidence-based results.

When should I run cross-feature regression testing in the software development lifecycle?▼

Cross-feature regression testing should be run after all individual features pass their tests and before release. This Skill executes system-wide verification during this phase to ensure integrated interactions and overall system behavior remain robust.

Does this system testing approach align with IEEE 829 and ISTQB best practices?▼

Yes, this system testing approach is explicitly aligned with IEEE 829 and ISTQB best practices. It enforces quality gates by requiring evidence-based test results for all SRS requirements, validating integrated system behavior and non-functional compliance.

What do I need to have completed before running comprehensive system testing?▼

Before running comprehensive system testing, all individual features must be developed and individually tested. This Skill then verifies cross-feature interactions, end-to-end workflows, and non-functional requirements to ensure the integrated system is production-ready.