تشغيل أي مهارة في Manus بنقرة واحدة

darwin-test-strategy

النجوم٧

التفرعات١

آخر تحديث٣ يونيو ٢٠٢٦ في ١١:١١

QE test strategy and execution workflow. Activates for Mode:test tasks or when writing and running tests independently without a Developer partner.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

The-Darwin-Project

The-Darwin-Project/Blackboard

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو ضمان جودة البرمجيات والمختبرونمهن الحاسوب والرياضيات·SOC 15-1253

SKILL.md

readonly

name	darwin-test-strategy
description	QE test strategy and execution workflow. Activates for Mode:test tasks or when writing and running tests independently without a Developer partner.
roles	["qe"]
modes	["implement","test"]

Darwin QE Test Strategy

When to Use

You are in test-only mode. FRIDAY wants you to write and/or run tests, NOT implement features.

Test Workflow

Understand the scope: Read the event document and any referenced code changes
Clone/pull the target repo: Always sync with the remote first
Write tests for the expected behavior:
- Python projects: use pytest with the project's existing test patterns
- Frontend changes: use repo Playwright tests for scripted assertions, or Playwright MCP for ad-hoc browser inspection (navigate, click, screenshot) without writing test code
- API changes: use available HTTP clients for endpoint verification
Run the tests: Execute and capture results
Report: Use team_send_results to deliver the test report

Output Format

## Test Report

### Test Plan
- What was tested and why

### Results
| Test | Status | Notes |
| ---- | ------ | ----- |
| test_name_1 | PASS | |
| test_name_2 | FAIL | Expected X, got Y |

### Summary
- X/Y tests passing
- Coverage gaps: <list any untested paths>
- Recommendation: <PASS / FAIL / NEEDS FIXES>

Rules

Do NOT implement features. You test, not build.
You MAY fix trivial bugs found during testing (typos, missing imports) -- document what you fixed.
If tests fail, report the failures clearly. Do NOT rewrite the implementation.
Commit test files to the feature branch ({type}/evt-{EVENT_ID}) so CI can pick them up.
Use team_send_results to deliver your test report to FRIDAY.

المزيد من هذا المستودع

نفس المستودع

darwin-dockerfile-safety

The-Darwin-Project/Blackboard

Safety rules for modifying Dockerfiles and Containerfiles. Use when editing container build files.

2026-07-217

darwin-reporting-context

The-Darwin-Project/Blackboard

MR/PR context gathering and diagnostic reporting guidelines. Activates when working on events that reference MRs/PRs or when reporting investigation findings.

2026-07-217

darwin-team-huddle

The-Darwin-Project/Blackboard

Team coordination for implement and test modes. Developer and QE use team_send_results for final reports, team_huddle for mid-task questions to FRIDAY.

2026-07-217

darwin-gitops

The-Darwin-Project/Blackboard

GitOps workflow rules for modifying infrastructure via git. Use when cloning repos, modifying Helm values, committing, pushing, or verifying deployments.

2026-07-137

darwin-mr-lifecycle

The-Darwin-Project/Blackboard

MR/PR lifecycle operations -- pipeline check, retest, merge, conflict reporting. Extends darwin-gitlab-ops.

2026-07-137

darwin-comms

The-Darwin-Project/Blackboard

Report findings and status updates to the Darwin FRIDAY. Use team_send_results for final reports (task modes). In message mode, use team_send_message instead.

2026-07-097

name	darwin-test-strategy
description	QE test strategy and execution workflow. Activates for Mode:test tasks or when writing and running tests independently without a Developer partner.
roles	["qe"]
modes	["implement","test"]

Darwin QE Test Strategy

When to Use

You are in test-only mode. FRIDAY wants you to write and/or run tests, NOT implement features.

Test Workflow

Understand the scope: Read the event document and any referenced code changes
Clone/pull the target repo: Always sync with the remote first
Write tests for the expected behavior:
- Python projects: use pytest with the project's existing test patterns
- Frontend changes: use repo Playwright tests for scripted assertions, or Playwright MCP for ad-hoc browser inspection (navigate, click, screenshot) without writing test code
- API changes: use available HTTP clients for endpoint verification
Run the tests: Execute and capture results
Report: Use team_send_results to deliver the test report

Output Format

## Test Report

### Test Plan
- What was tested and why

### Results
| Test | Status | Notes |
| ---- | ------ | ----- |
| test_name_1 | PASS | |
| test_name_2 | FAIL | Expected X, got Y |

### Summary
- X/Y tests passing
- Coverage gaps: <list any untested paths>
- Recommendation: <PASS / FAIL / NEEDS FIXES>

Rules

Do NOT implement features. You test, not build.
You MAY fix trivial bugs found during testing (typos, missing imports) -- document what you fixed.
If tests fail, report the failures clearly. Do NOT rewrite the implementation.
Commit test files to the feature branch ({type}/evt-{EVENT_ID}) so CI can pick them up.
Use team_send_results to deliver your test report to FRIDAY.