Explain monitored-system over-plan legitimacy

This commit is contained in:
rcourtman 2026-04-15 13:38:57 +01:00
parent a33983175b
commit 8d703f2371
14 changed files with 320 additions and 17 deletions

View file

@ -15,6 +15,7 @@ const MONITORED_SYSTEM_ENTITLEMENTS = {
current_available: true,
available_slots: 0,
overage: 11,
reason: "preexisting_usage",
blocks_new_systems: true,
existing_monitoring_continues: true,
},
@ -45,6 +46,7 @@ const MONITORED_SYSTEM_RUNTIME_CAPABILITIES = {
current_available: true,
available_slots: 0,
overage: 11,
reason: "preexisting_usage",
blocks_new_systems: true,
existing_monitoring_continues: true,
},
@ -108,6 +110,7 @@ const MONITORED_SYSTEM_COMMERCIAL_POSTURE = {
current_available: true,
available_slots: 0,
overage: 11,
reason: "preexisting_usage",
blocks_new_systems: true,
existing_monitoring_continues: true,
},
@ -252,6 +255,11 @@ async function openPageWithUrgentMonitoredSystemBanner(page: Page) {
await expect(
page.getByRole("status").filter({ hasText: "over plan by 11" }),
).toBeVisible();
await expect(
page.getByRole("status").filter({
hasText: "exceeded the limit before new monitored systems were blocked",
}),
).toBeVisible();
}
test.describe("Monitored-system billing focus", () => {