Add NUnit + Reqnroll + Playwright BrowserStack SDK sample

[saraswati-padmawar]

Populates this customer-facing sample repo (previously skeleton: README + CODEOWNERS + Semgrep only) with a working NUnit + Reqnroll + Playwright (C#) sample driven by the BrowserStack .NET SDK.

What's included

• Features/Sample.feature + StepDefinitions/SampleSteps.cs — public bstackdemo.com add-to-cart scenario
• Features/LocalSample.feature + StepDefinitions/LocalSampleSteps.cs — BrowserStack Local scenario (bs-local.com:45454)
• Hooks/PlaywrightHooks.cs — creates IPage per scenario (SDK routes Chromium.LaunchAsync())
• browserstack.yml — credentials, platforms, Local toggle, framework: nunit
• .sln / .csproj (Reqnroll.NUnit + NUnit + Microsoft.Playwright.NUnit + BrowserStack.TestAdapter), .gitignore, sanity-workflow.yml, README

References

• Direct adaptation of browserstack/xunit-reqnroll-playwright-browserstack, swapping the xUnit runner for NUnit (packages + Assert.That assertions + framework: nunit)
• NUnit package set aligned with browserstack/csharp-playwright-browserstack
• Follows the standardized Automate sample template (Confluence: SDK Sample Repo Generator, R1–R4)

Verified on BrowserStack ✅

Built and ran both scenarios end-to-end against BrowserStack Automate (.NET 8, arm64), passing on the configured platforms (Windows 11/chrome, OS X Ventura/playwright-webkit):

Scenario	Command	Result
Public (bstackdemo add-to-cart)	dotnet test --filter ~BStackDemoCart	✅ passed (build e42c67df4402e6c1e6f997209241f07536535e08)
BrowserStack Local (bs-local.com:45454)	dotnet test --filter ~BStackLocalSample	✅ passed (SDK tunnel; title assertion passed)

Reqnroll generated the NUnit tests from the .feature files. Project: BrowserStack Samples.

Note from verification: the SDK's auto-generated patch references the Microsoft.Playwright.NUnit namespace, so Microsoft.Playwright.NUnit is required in the .csproj (without it dotnet build fails CS0234) — added in this PR.

🤖 Generated with Claude Code

[Rohannagariya1]

LGTM ✅ — solid NUnit/Reqnroll adaptation, both scenarios verified. Approving.

A few low-risk, optional cleanups (non-blocking):

• System.Net.Http 4.3.4 and System.Text.RegularExpressions 4.3.1 in the .csproj are in-box on net8.0 and unnecessary — safe to drop (and they're the kind of legacy refs Semgrep/dependabot tend to flag).
• browserstack.yml is missing testReporting: true (+ the reporting comment block) that both Node siblings include — minor cross-sample consistency.
• The workflow's "completed" step calls checks.create again rather than updating the in-progress run, so you get one stuck in_progress + one completed check. Copied from the xunit reference, so low priority.
• [id="\31 "] works but is inconsistent with the plain [id="1"] attribute selector used in the JS samples — purely cosmetic.