long-task-feature-st

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

Execute black-box acceptance tests via Chrome DevTools MCP and generate ISO/IEC/IEEE 29119 compliant documents.

178|43|Updated Feb 12, 2026

Search Tags:#automation #testing #acceptance testing #black-box testing #chrome devtools mcp #iso 29119

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the rigorous process of black-box acceptance testing for completed software features, ensuring they meet user and system requirements before review.

Core Features & Use Cases

Environment Management: Manages test environment lifecycle (start, cleanup, restart) via env-guide.md.
Test Execution: Executes black-box acceptance tests using Chrome DevTools MCP for UI features.
Documentation Generation: Creates ISO/IEC/IEEE 29119 compliant test case documents with traceability.
Use Case: After a feature passes TDD and quality gates, this Skill runs all defined acceptance tests, verifies UI interactions, checks for console errors, and documents the results, flagging any failures for immediate attention.

Quick Start

Use the long-task-feature-st skill to run black-box acceptance testing for the 'user-profile-update' feature.

Frequently Asked Questions about long-task-feature-st

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

FAQPage Schema

How do I automate black-box acceptance testing for UI features?▼

Automating black-box acceptance testing involves executing UI interactions via Chrome DevTools MCP, validating feature adherence to SRS and UCD specifications, and generating compliant test case documents.

What is ISO 29119 compliance in test case documentation?▼

ISO 29119 compliance in test case documentation ensures that generated test records follow standardized software testing guidelines, providing traceability and structured reporting for black-box acceptance testing lifecycles.

Can I use Chrome DevTools MCP to validate UI interactions and check for console errors?▼

Yes, Chrome DevTools MCP is used to execute black-box acceptance tests, verifying UI interactions and checking for console errors against defined specifications during the post-quality gate testing phase.

How do I manage the test environment lifecycle during acceptance testing?▼

Test environment lifecycle management during acceptance testing is handled through environment start, cleanup, and restart procedures defined within the testing framework's environment configuration references.

When should I run black-box acceptance tests after passing TDD quality gates?▼

Black-box acceptance tests should be run immediately after a feature passes TDD and quality gates to validate external behavior, verify UI interactions, check console errors, and flag any failures for review.

What are the limitations of using Chrome DevTools MCP for black-box testing?▼

Chrome DevTools MCP for black-box testing is limited to UI features and external observation, meaning it cannot validate internal code paths, non-UI system components, or backend logic not exposed through the interface.