Add Dashboard integration tests with Reqnroll, Playwright, and Shouldly

[Copilot]

Implements BDD integration tests for Dashboard functionality covering role-based access (Administrator, Estate, Viewer) with assertions against hardcoded test data.

New Test Project: EstateManagementUI.IntegrationTests

Feature File (Features/Dashboard.feature)

• 9 scenarios testing role-based dashboard visibility and data display
• Administrator: dashboard view only, no KPIs/data
• Estate/Viewer: full access to KPIs, sales data, comparison selectors

Test Infrastructure

• Hooks/BrowserHooks.cs: Playwright lifecycle (browser setup, screenshot capture on failure)
• Steps/DashboardSteps.cs: Gherkin step bindings to page interactions
• Common/DashboardPageHelper.cs: Page object pattern with Playwright locators and Shouldly assertions

Test Data Assertions

Values from TestMediatorService.cs:

And the Merchants with Sales in Last Hour shows "45"
And the Merchants with No Sales Today shows "12"
And the Merchants with No Sales in Last 7 Days shows "5"
And the Today's Sales card shows "523" transactions
And the Failed Sales card shows "15" transactions

Notes

Application startup logic intentionally excluded per requirements - to be implemented separately. Tests ready to run once app configured for test mode.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Dashboard Integration Testing</issue_title>
<issue_description>I want a suite of integration tests built for the Blazor Server Application.

The first set of tests will be for the Dashboard.

Can you build the tests based on the functionality available in terms of user roles (Admin/Estate/Viewer), I want these tests to have assertions based on the hard coded test data that's in the application (this can be swapped out at a later date)

Any assertions will be done with the Shouldly framework.

I must stress that the only code I am expecting from this is:

A reqnroll feature file
A hooks file to allow control of the browser application (based on playwright)
A file with steps to control the browser application
A file that links the feature file to the application steps code

I will deal with how the application actually gets started up for the testing at a later point

</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Dashboard Integration Testing #581

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[StuartFerguson]

@copilot looks pretty good, one tweak though can u rename the project EstateManagementUI.IntegrationTests

[Copilot]

@copilot looks pretty good, one tweak though can u rename the project EstateManagementUI.IntegrationTests

Done! Project renamed to EstateManagementUI.IntegrationTests including all namespaces and references. Commit: 3af8226