full-hardening-run

Automate end-to-end hardening of Playwright E2E tests and websocket resilience.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/aaravjj2/tradingview-recreation --skill full-hardening-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-hardening-run
Source: https://github.com/aaravjj2/tradingview-recreation/tree/main/.agent/skills/full-hardening-run
Command: npx skills add https://github.com/aaravjj2/tradingview-recreation --skill full-hardening-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined framework to eliminate flaky tests and harden websocket and E2E workflows, culminating in 0 failed / 0 skipped with verifiable evidence.

Core Features & Use Cases

  • End-to-end stabilization of Playwright-headed Chrome E2E tests.
  • Hardened WebSocket reconnection and diagnostic tooling.
  • Enforced data-testid contracts and evidence-driven validation.

Quick Start

Execute the full hardening plan across your repository to ensure deterministic tests with zero failures and documented evidence.

Frequently Asked Questions about full-hardening-run

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

FAQPage Schema
How do I eliminate flaky Playwright E2E tests and achieve zero failures in CI?

To eliminate flaky Playwright E2E tests, apply a phase-driven hardening framework that stabilizes headed Chrome executions and enforces UI contracts with verifiable evidence across CI pipelines.

What is the best way to harden websocket reconnection logic for E2E test stability?

Hardening websocket reconnection involves automating diagnostic tooling and resilience checks to prevent connection drops from causing test failures, ensuring deterministic end-to-end workflows with documented proof of stability.

How do I enforce data-testid contracts in Playwright tests to prevent UI breakage?

Enforcing data-testid contracts in Playwright requires an evidence-driven validation process that checks UI elements against defined selectors, ensuring phase-driven execution and traceability across your CI pipeline.

Does this E2E hardening approach work with headed Chrome browsers in CI pipelines?

Yes, this E2E hardening approach works with headed Chrome browsers in CI pipelines by applying automated end-to-end stabilization and proof-based validation to achieve zero skipped or failed tests.

Why do my websocket E2E tests keep failing intermittently during CI execution?

Intermittent websocket E2E test failures often stem from unhandled connection drops and flaky UI selectors; applying automated hardening with diagnostic tooling and strict test-id enforcement resolves these instability issues.