sdcorejs-testing-e2e-angular-portal

Generate happy-path E2E testing specs for Angular Portal features.

2|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-testing-e2e-angular-portal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdcorejs-testing-e2e-angular-portal
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/sdcorejs-testing-e2e-angular-portal
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-testing-e2e-angular-portal

SYSTEM DOCUMENTATION & REQUIREMENTS

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".

Frequently Asked Questions about sdcorejs-testing-e2e-angular-portal

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

FAQPage Schema
How do I generate E2E tests for an Angular portal after creating CRUD features?

To generate E2E tests for an Angular portal, use this Skill after your feature code is written. It automatically creates happy-path testing specs that validate list rendering, navigation, form validation, and workflow actions for your new CRUD modules.

Can I use Playwright for E2E testing if my Angular portal project already uses Cypress?

You can use Playwright or Cypress for E2E testing because the Skill detects your project's configured test runner. It follows your existing framework conventions instead of introducing a second framework, ensuring your test suite remains consistent.

What does happy-path E2E testing cover for Angular portal workflows?

Happy-path E2E testing covers core user journeys including list-to-create navigation, update and detail routing, required form validation, and key workflow actions. It applies realistic user flows to verify integration and routing behaviors that unit tests often miss.

What is the best way to ensure stable E2E test assertions in an Angular portal?

The best way to ensure stable E2E test assertions is by using data-test selectors, waiting for network conditions to settle, and preferring seed or mock data. The Skill enforces these conventions to prevent flaky tests and reports actionable failures.

Do I need to write code for an Angular portal feature before generating E2E tests?

You need to complete the Angular portal code generation for your CRUD and workflow features before generating E2E tests. The Skill applies after code generation finishes to validate the actual implementation, including routing, guards, and form integration.