task-module-testing

Automating module testing task execution requires a two-tier skill loading workflow that retrieves plan tasks, loads domain testing skills from task.skills, and drives test construction, implementation, and verification. You initiate this by providing a plan_id and task_number.

Two-tier skill loading for module testing is a mechanism that first loads Tier 1 system skills, then dynamically loads Tier 2 domain testing skills specified in task.skills. This layered approach enables domain-agnostic test planning and verification across different languages and frameworks.

To execute a module_testing profile task, provide the plan-marshall plan_id and task_number. The executor automatically applies the two-tier loading workflow to retrieve required domain testing skills, construct the tests, implement them, and verify results against management contracts.

The module testing executor supports domain-specific testing frameworks through its two-tier loading architecture. It dynamically loads required domain testing skills from the task.skills field specified in your plan, allowing it to adapt to various languages and frameworks.

A domain-agnostic module testing task produces execution summaries and verification results. These outputs are explicitly aligned with the Task Execution Contract and Task Contract to ensure test implementation and verification results meet management requirements.

No external dependencies are required to run the module testing task executor. It operates as a standalone domain-agnostic executor, relying solely on the plan_id, task_number, and the domain testing skills defined within the task.skills configuration.