원클릭으로 Manus에서 모든 스킬 실행

시작하기

e2e-verification

스타0

포크0

업데이트2026년 7월 21일 08:37

Activate this skill when verifying changes, running E2E tests, or checking DoD requirements before PR creation.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

peterrichards-lr

peterrichards-lr/liferay-ai-commerce-accelerator

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

E2E Verification & Definition of Done

Before any feature, bugfix, or issue can be considered "code complete", the agent must ensure that all integration and verification gates pass.

1. Automated E2E Testing

Run the local E2E Playwright test suite against a real Liferay DXP container:

bash scripts/run-e2e-ldm.sh -v -k --ci

Before declaring any feature or bugfix 'code complete', you MUST execute run_command to invoke the command above, and END your turn. You are FORBIDDEN from declaring the task finished or pushing PRs until you receive the output confirming the E2E verification succeeded.

2. Post-Completion "Definition of Done"

Test Protocol: Provide 3-5 manual/automated steps to verify in a live Liferay instance.
Redundancy Scan: After a feature is complete, scan for any newly introduced duplicate code.
Strategic Deployment Control (No Automatic Deploy): Do not run or suggest deploy tasks as part of a general "build" command.
Dependency Awareness: Before deployment, list the required order of execution (e.g., 1. OAuth2 CX, 2. Batch CX for Objects, 3. Frontend Custom Element).
Manual Trigger: Always end a feature cycle by asking: "The code is ready and tested. Would you like me to provide the specific build/deploy commands for this extension now?"

Last Updated: 2026-07-19 | Last Reviewed: 2026-07-19

이 저장소의 다른 Skills

같은 저장소

coding-standards

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when writing or refactoring microservice and SDK javascript/typescript source files.

2026-07-220

human-in-the-loop

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill before opening pull requests, modifying production configurations, or executing deployment and destructive commands to ensure proper human-in-the-loop verification.

2026-07-220

reflection-and-planning

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when beginning complex tasks, proposing architectural changes, or modifying codebase files to ensure proper planning and predictive failure analysis.

2026-07-220

tool-use-react

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when making tool calls, interacting with the terminal, or invoking GitHub APIs to ensure strict ReAct patterns are followed.

2026-07-220

multi-agent-orchestration

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill when delegating tasks, defining subagents, or orchestrating parallel agentic workflows.

2026-07-220

documentation

peterrichards-lr/liferay-ai-commerce-accelerator

Activate this skill after implementing code changes to verify, review, and update markdown documentation and timestamps.

2026-07-210

name	e2e-verification
description	Activate this skill when verifying changes, running E2E tests, or checking DoD requirements before PR creation.

E2E Verification & Definition of Done

Before any feature, bugfix, or issue can be considered "code complete", the agent must ensure that all integration and verification gates pass.

1. Automated E2E Testing

Run the local E2E Playwright test suite against a real Liferay DXP container:

bash scripts/run-e2e-ldm.sh -v -k --ci

2. Post-Completion "Definition of Done"

Test Protocol: Provide 3-5 manual/automated steps to verify in a live Liferay instance.
Redundancy Scan: After a feature is complete, scan for any newly introduced duplicate code.
Strategic Deployment Control (No Automatic Deploy): Do not run or suggest deploy tasks as part of a general "build" command.
Dependency Awareness: Before deployment, list the required order of execution (e.g., 1. OAuth2 CX, 2. Batch CX for Objects, 3. Frontend Custom Element).
Manual Trigger: Always end a feature cycle by asking: "The code is ready and tested. Would you like me to provide the specific build/deploy commands for this extension now?"

Last Updated: 2026-07-19 | Last Reviewed: 2026-07-19