Getting started with WAVit Dashboard

• Azure DevOps: read access to the WavitSystems project.
• The dev Key Vault: permission to read its secrets, for the account you use with az login. Ask for the vault's URI as well. It goes into your Development settings.
• The dev databases: the app uses two SQL Server databases, MiPoint and the Identity database. Their connection strings come from the vault, so your machine must be able to reach the server they name.
• A dev test login: an email and password in the dev Identity database. The email must be confirmed and have a master MID record with at least one active unit. Never use a real merchant's login.

git clone https://micampdev.visualstudio.com/WavitSystems/_git/WAVitDashboard
cd WAVitDashboard
git switch development
git switch -c us/<story-id>/main

dotnet restore WAVitDashboard.sln
dotnet build WAVitDashboard.sln

• Branches are named after the work item: us/<story-id>/main for a story, us/<story-id>/task/<task-id>-<short-name> for a task under it.
• The solution has four projects: WAVitDashboard/WAvitDashboardWeb.csproj (the web app), MiCamp.Models and MiCamp.DataAccess (MiPoint entities and data access), and WAVitDashboard.Tests.
• The build prints a few hundred warnings, nearly all about nullable references. They are expected. Errors are not.

{
  "KeyVault": {
    "Uri": "https://<dev-key-vault-name>.vault.azure.net/"
  },
  "Clarity": {
    "ProjectId": ""
  }
}

The file is listed in .gitignore, so it stays on your machine. Every launch profile sets ASPNETCORE_ENVIRONMENT to Development, and that is what makes the app load it. An environment variable named KeyVault__Uri works too. User secrets are not set up (the project has no UserSecretsId), and the app never reads connection strings from configuration anyway.

az login                          # the account that can read the dev vault
dotnet dev-certs https --trust    # once per machine
dotnet run --project WAVitDashboard --launch-profile https

The browser opens on the public landing page. Before you sign in, open /health to check that the app reached the vault and both databases. It answers 200 when every check passes and 503 when one fails. It shows statuses only; the reason for a failure is logged in the console where dotnet run is running.

{
  "status": "Healthy",
  "checks": [
    { "name": "identity-db", "status": "Healthy" },
    { "name": "mipoint-db", "status": "Healthy" },
    { "name": "key-vault", "status": "Healthy" }
  ]
}

1. 1
   Sign inGo to https://localhost:7036/Identity/Account/Login, or use the sign-in link on the landing page, and sign in with the dev test login. Every successful sign-in lands on Home, /Dashboard/Portal/Home, whatever page you started from.
2. 2
   Check HomeHome fills in after two background requests: today's balance, the 10-day chart and a card for each unit. Zero balances are normal when the dev units took no payments today.
3. 3
   Open TransactionsChoose Transactions in the navigation (/Dashboard/Transaction/Index). The page opens on today's date range for every unit your login can see.
4. 4
   Widen the rangePick Last 7 Days (or Custom) and press Search. The summary strip and the table reload with the payments in range.
5. 5
   Open one paymentUse Quick View for the side panel, or Details for the full transaction page, which opens in a new tab.

dotnet build WAVitDashboard.sln --configuration Release
dotnet test WAVitDashboard.Tests/WAVitDashboard.Tests.csproj --configuration Release --no-build

On development at 2ccf8cf this runs 151 tests, and all of them pass. Pull requests into development and main run the same restore, build and test (azure-pipelines.yml). Every push to development runs the tests again before it deploys to the dev site.

A Playwright end-to-end suite, WAVitDashboard.E2E, lives on unmerged branches (the newest is us/1693/main). It reads E2E_BASE_URL, E2E_USER and E2E_PASSWORD from a .env file that you copy from .env.example, it must never point at production, and no pipeline runs it yet.