Run any Skill in Manus with one click

testing-unit-integration-system

Stars0

Forks0

UpdatedApril 23, 2026 at 20:17

Use when: creating or updating test coverage across unit, integration, and system/end-to-end levels for application features and modules.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

berthelemy

berthelemy/talaris-project-toolkit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	testing-unit-integration-system
description	Use when: creating or updating test coverage across unit, integration, and system/end-to-end levels for application features and modules.

Unit, Integration, and System Testing

Goal

Provide layered automated test coverage with clear confidence boundaries.

Test Layers

Unit tests: isolate classes/functions and edge cases with mocks/stubs.
Integration tests: verify DB, services, internal APIs, and module interactions.
System tests: validate user workflows end-to-end through HTTP/UI boundaries.

Do

Add tests for both success paths and failure/authorization cases.
Cover locking behavior, autosave behavior, and audit logging side effects.
Keep fixtures deterministic and teardown clean.
Name tests by behavior, not implementation detail.

Checks

New features include at least one test at the most appropriate layer.
Regressions include a failing test before the fix where feasible.
Test suite can run in CI without environment-specific hacks.

More from this repository

same repository

kanban-methodology-best-practices

berthelemy/talaris-project-toolkit

Use when: planning, executing, or reviewing delivery work using Kanban boards, WIP limits, pull-based flow, and continuous improvement practices.

2026-05-160

accessibility-wcag22-aa

berthelemy/talaris-project-toolkit

Use when: designing, building, or reviewing UI to meet WCAG 2.2 Level AA accessibility requirements across forms, navigation, content, and interactions.

2026-04-230

authentication-authorization-rbac

berthelemy/talaris-project-toolkit

Use when: implementing login, session controls, role-based access control, and permissions across system, programme, project, and module contexts.

2026-04-230

autosave-live-persistence

berthelemy/talaris-project-toolkit

Use when: implementing immediate backend persistence from frontend edits without full form submission, including validation and failure handling.

2026-04-230

codeigniter-architecture-patterns

berthelemy/talaris-project-toolkit

Use when: designing or refactoring feature architecture in CodeIgniter for maintainability, separation of concerns, and module consistency.

2026-04-230

dashboards-reporting

berthelemy/talaris-project-toolkit

Use when: building programme/project dashboards, drill-down detail views, and cross-module reports with traceable source links.

2026-04-230

name	testing-unit-integration-system
description	Use when: creating or updating test coverage across unit, integration, and system/end-to-end levels for application features and modules.

Unit, Integration, and System Testing

Goal

Provide layered automated test coverage with clear confidence boundaries.

Test Layers

Unit tests: isolate classes/functions and edge cases with mocks/stubs.
Integration tests: verify DB, services, internal APIs, and module interactions.
System tests: validate user workflows end-to-end through HTTP/UI boundaries.

Do

Add tests for both success paths and failure/authorization cases.
Cover locking behavior, autosave behavior, and audit logging side effects.
Keep fixtures deterministic and teardown clean.
Name tests by behavior, not implementation detail.

Checks

New features include at least one test at the most appropriate layer.
Regressions include a failing test before the fix where feasible.
Test suite can run in CI without environment-specific hacks.