skills.rest
AGIBuild
AGIBuildCOMMUNITY
Explore all skills by this author →
GitHub

dotnet-playwright

Automate end-to-end browser testing for .NET applications with Playwright.

10|Updated Jan 28, 2026
Search Tags:#browser automation#codegen#dotnet#playwright#e2e testing#ci#trace viewer
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-playwright
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-playwright
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-playwright
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-playwright

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation and execution of end-to-end browser tests for .NET applications, ensuring your web UIs function correctly across different browsers and scenarios.

Core Features & Use Cases

  • Automated Browser Testing: Write and run E2E tests using Playwright for Chromium, Firefox, and WebKit.
  • CI Integration: Optimize build times with Playwright browser caching in CI environments.
  • Debugging Tools: Leverage trace viewing and codegen for faster test development and troubleshooting.
  • Use Case: Automatically test the entire user registration flow of your .NET web application, verifying that new users can sign up, receive a confirmation email, and log in successfully.

Quick Start

Use the dotnet-playwright skill to write an end-to-end test for your web application's login page.

Frequently Asked Questions about dotnet-playwright

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

FAQPage Schema
How do I write end-to-end tests for a .NET web application?▼

You can write end-to-end tests for a .NET web application by using Playwright to automate browser lifecycle management, handle page interactions, and apply assertions across Chromium, Firefox, and WebKit. It also provides codegen for scaffolding tests.

Does Playwright E2E testing support WebKit and Firefox for .NET 8.0 apps?▼

Playwright E2E testing supports Chromium, Firefox, and WebKit browsers for .NET 8.0+ applications. It facilitates cross-browser page interactions and automated UI assertions without requiring additional browser automation frameworks.

What's the best way to debug a failing Playwright browser automation test?▼

The best way to debug a failing Playwright browser automation test is by using the integrated trace viewer. This tool records page interactions and assertions, allowing you to review test execution step-by-step to identify and troubleshoot failures.

How do I optimize E2E test execution time in CI environments?▼

To optimize E2E test execution time in CI environments, configure Playwright browser caching. This stores downloaded browser binaries between runs, reducing setup overhead and speeding up your .NET build pipelines.

Can I automatically generate test scaffolding for my .NET web UI?▼

Yes, you can automatically generate test scaffolding for your .NET web UI using the Playwright codegen feature. It records your browser interactions and translates them into executable E2E test code for faster test development.

Related Skills

Explore More Software Engineering Skills→
wshaddixwshaddix
71

dotnet-playwright

Automate browser testing for .NET applications using Playwright.

Community
Intermediate
rudironsonirudironsoni

dotnet-playwright

Automate browser interactions and end-to-end tests for .NET applications with Playwright.

Community
Intermediate
furrycolombia-sysfurrycolombia-sys
1

run-e2e

Run Playwright end-to-end tests across multiple browsers.

Community
Advanced
wshaddixwshaddix
71

dotnet-wpf-migration

Guide desktop application migration from .NET Framework to modern .NET and WinUI.

Community
Advanced