Playwright C# BDD Framework using claude opus
Budget: $10 – $30 USD
I need a robust Playwright-based automation framework written in C# that follows the opus oe sonet model from Claude and embraces a full BDD workflow. The framework must suit my “Automation framework” target rather than being tied to just one platform, so while web support is the priority, I want the architecture to stay open for possible mobile or desktop extensions.
The main focus is on end-to-end automation test coverage, yet the code structure should remain flexible enough that future performance or security layers could drop in without a rewrite. All test logic will live in readable .feature files, with step definitions, hooks, and a central object repository generated automatically.
Key deliverables
• Framework source in C# (.NET 6 or later) integrating Playwright
• CLI or UI utility that scaffolds new .feature files, page objects, hooks, and trace configuration
• Self-healing element mechanism: when a locator breaks, the framework must search alternative attributes and update the repository automatically, logging the change
• Consolidated execution report in HTML (pass/fail stats, screenshots, Playwright traces) produced at run-time
• Sample feature set that demonstrates login, search, and a negative path scenario
• README explaining setup, execution, and how to extend keywords, data sets, and hooks
Acceptance criteria
1. Running `dotnet test` against the sample suite executes headless and headed runs with Playwright, creates a fresh report, and stores traces.
2. Breaking a locator in the sample page object triggers the self-healing logic and the test still passes, with the update reflected in the repository file.
3. A contributor can generate a new scenario with one command, receiving stubbed steps, page class, and hook template ready for editing.
Use any auxiliary libraries you need (e.g., SpecFlow for BDD, FluentAssertions for checks, Allure or ReportUnit for reports) as long as licensing stays permissive. Keep the code lightweight, well-commented, and immediately runnable after a `dotnet restore`.
Deliver everything in a Git repository so I can review commits, run the suite locally, and integrate it into my pipeline.
The main focus is on end-to-end automation test coverage, yet the code structure should remain flexible enough that future performance or security layers could drop in without a rewrite. All test logic will live in readable .feature files, with step definitions, hooks, and a central object repository generated automatically.
Key deliverables
• Framework source in C# (.NET 6 or later) integrating Playwright
• CLI or UI utility that scaffolds new .feature files, page objects, hooks, and trace configuration
• Self-healing element mechanism: when a locator breaks, the framework must search alternative attributes and update the repository automatically, logging the change
• Consolidated execution report in HTML (pass/fail stats, screenshots, Playwright traces) produced at run-time
• Sample feature set that demonstrates login, search, and a negative path scenario
• README explaining setup, execution, and how to extend keywords, data sets, and hooks
Acceptance criteria
1. Running `dotnet test` against the sample suite executes headless and headed runs with Playwright, creates a fresh report, and stores traces.
2. Breaking a locator in the sample page object triggers the self-healing logic and the test still passes, with the update reflected in the repository file.
3. A contributor can generate a new scenario with one command, receiving stubbed steps, page class, and hook template ready for editing.
Use any auxiliary libraries you need (e.g., SpecFlow for BDD, FluentAssertions for checks, Allure or ReportUnit for reports) as long as licensing stays permissive. Keep the code lightweight, well-commented, and immediately runnable after a `dotnet restore`.
Deliver everything in a Git repository so I can review commits, run the suite locally, and integrate it into my pipeline.