skills.rest
martiendejong
martiendejongCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

integration-testing

Configure Playwright tests and capture findings in ClickUp across phased workflows.

1|Updated Jan 11, 2026
Search Tags:#automation#testing#e2e#qa#playwright#clickup
One-click install
npx skills add https://github.com/martiendejong/autonomous-dev-system --skill integration-testing-martiendejong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integration-testing
Source: https://github.com/martiendejong/autonomous-dev-system/tree/main/.claude/skills/integration-testing
Command: npx skills add https://github.com/martiendejong/autonomous-dev-system --skill integration-testing-martiendejong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end testing across web projects using Playwright, capturing evidence, surfacing failures, and triaging issues in ClickUp to accelerate QA cycles.

Core Features & Use Cases

  • End-to-end browser automation for any project
  • Automatically create ClickUp issues for findings and attach evidence
  • Self-improve test patterns over time with a learning loop
  • Phase-driven workflow: project discovery, health checks, task analysis, Playwright testing, and reporting

Quick Start

Start an integration test by invoking the skill in qa mode against a project, and it will auto-discover tests, run Playwright automation, and report results.

Frequently Asked Questions about integration-testing

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

FAQPage Schema
How do I automate end-to-end testing with Playwright and ClickUp?▼

End-to-end testing with Playwright and ClickUp is automated by discovering the target project, configuring tests, executing browser automation, and auto-triaging failures into ClickUp tasks with evidence attached.

Can I automatically create ClickUp issues for failed Playwright tests?▼

Yes, failed Playwright tests automatically generate ClickUp issues. The skill captures evidence, surfaces failures, and triages issues directly into ClickUp to accelerate the QA reporting cycle.

What is the workflow for running e2e browser automation against a web project?▼

The e2e browser automation workflow operates across phases: project discovery, health checks, task analysis, Playwright execution, and reporting, ensuring outputs include test plans, evidence, and issue comments.

Does this testing approach improve test patterns over time?▼

Yes, the testing approach includes learning loops that self-improve test patterns over time, using data from previous Playwright executions and reporting phases to enhance future QA runs.

Do I need to manually configure test plans before running Playwright automation?▼

No, manual configuration is not needed. Invoking the skill in QA mode auto-discovers tests, runs the Playwright automation, prepares the target project, and generates the required test plans automatically.

What evidence is captured during Playwright test execution for issue triage?▼

During Playwright test execution, the skill captures evidence and prepares ClickUp integration to report findings. Outputs include detailed test plans, execution evidence, and issue comments for triage.

Related Skills

Explore More Software Engineering Skills→
bybren-llcbybren-llc
395

testing-patterns

Standardize Jest and Playwright tests with RLS-aware fixtures and Linear evidence templates.

Official
Intermediate
KodingDevKodingDev
5

debug

Identify and resolve root causes of bugs and test failures.

Community
Advanced
markus41markus41
12

power-automate-flows

Create, manage, and deploy Power Automate cloud flows via the Dataverse Web API.

Community
Advanced
devopstalesdevopstales
1

playwright

Automate Playwright browser tests and capture screenshots and traces.

Community
Intermediate