Playwright + C#
+ NUnit Framework

The Purpose

Playwright + C# is the expected stack in any Microsoft-ecosystem organisation: .NET shops, Azure DevOps pipelines, and teams already invested in the C# toolchain. Hiring managers in these environments look for native async/await fluency, NUnit familiarity, and the ability to structure a test project as a proper .NET solution.

This is Stack 5 of the Cross-Stack Series — the same QA Lab target tested with Playwright but in C# rather than TypeScript. Both stacks use the identical Playwright engine, making this a clean apples-to-apples comparison of language ecosystem fit, not automation capability.

Stack choice is an engineering decision, not brand preference. This framework demonstrates what idiomatic C# automation looks like — strongly typed, compiled, zero sync-over-async anti-patterns.

Architecture Constraints

Every decision reflects real .NET enterprise requirements:

• Strongly-typed Page Object Model — IPage dependency injection, no static state
• Native async/await throughout — await page.ClickAsync() is idiomatic, not bolted on
• NUnit [TestCase] — parametrized tests without DataProvider boilerplate
• [Parallelizable(ParallelScope.Self)] — parallel-safe, each class gets its own IPage
• Expect() for all assertions — not Assert.That() on raw strings
• TreatWarningsAsErrors in .csproj — code quality discipline expected in enterprise
• C# records for test data (FormData.cs) — immutable, value-equality, concise
• Environment variable for BASE_URL — zero hardcoded URLs in test code