test-ui

Automate end-to-end UI validation for fintech app pages with Playwright.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sperezintexas/fintech-app --skill test-ui-sperezintexas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-ui
Source: https://github.com/sperezintexas/fintech-app/tree/main/.cursor/skills/test-ui
Command: npx skills add https://github.com/sperezintexas/fintech-app --skill test-ui-sperezintexas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end UI testing validates that core pages and flows render correctly, catching regressions before release.

Core Features & Use Cases

  • Smoke tests for Home/Dashboard, Holdings, and Alerts
  • Structured test organization using test.describe and test() blocks, with clear setup, actions, and assertions
  • Easy extension: add new page tests by creating additional spec files and shared helpers

Quick Start

Start Playwright E2E tests by running the test:e2e script to validate the UI.

Frequently Asked Questions about test-ui

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

FAQPage Schema
How do I run Playwright e2e UI tests for core app pages?

Run Playwright e2e UI tests by executing the test:e2e script. This validates core pages like Home/Dashboard, Holdings, and Alerts to catch regressions before release.

What do I need to set up before running Playwright e2e tests?

Playwright e2e tests require a valid Playwright configuration and a running dev server with SKIP_AUTH enabled. Tests must be located under the tests directory and organized with test.describe blocks.

Can I extend e2e UI testing to cover new pages and flows?

Yes, you can extend e2e UI testing by creating additional spec files and shared helpers. Structure new page tests using test.describe and test blocks with clear setup, actions, and assertions.

What is the best way to organize test automation for a fintech app?

Organize test automation using structured test.describe and test blocks under the tests directory. This approach separates setup, actions, and assertions for core flows like xStrategyBuilder and Automation.

Why does my Playwright UI testing fail to authenticate on the dev server?

Playwright UI testing fails if SKIP_AUTH is not enabled on the dev server. The test configuration requires this environment flag to bypass authentication and validate page loads successfully.