sdcorejs-testing-e2e-angular-portal

What problem does it solve?

Ensures Angular Portal features work end-to-end in the browser by generating happy-path E2E tests after feature code is written, catching routing, guard, form, and integration issues that unit tests often miss.

Core Features & Use Cases

• Framework detection (Cypress vs Playwright): Detects the configured test runner in the target project and follows its conventions instead of introducing a second framework.
• Happy-path CRUD coverage: Creates list/create/update/delete E2E specs with realistic user flows and validations for required fields.
• Navigation and workflow actions: Validates list-to-create/edit navigation and extends coverage for workflow/action flows when the feature includes them.
• Conventions-aware test implementation: Uses data-test selectors when available, waits for load/network conditions appropriately, and prefers seed/mock data for stable assertions.

Use cases: After generating an Angular Portal entity feature (init-entity, list/detail screens, or workflow actions), generate E2E specs that verify the core user journey and key UI behaviors.

Quick Start

Use the skill to write E2E tests for the just-built Angular Portal feature by asking: "viết e2e test angular cho module/feature này".