mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-19 02:28:59 +00:00
Explain monitored-system counting on the plan surface
This commit is contained in:
parent
0080108fa8
commit
41ef7b2830
6 changed files with 50 additions and 2 deletions
|
|
@ -373,6 +373,17 @@ async function openMonitoredSystemUpgradeArrival(page: Page) {
|
|||
"aria-selected",
|
||||
"true",
|
||||
);
|
||||
await expect(
|
||||
page.getByText(
|
||||
"Pulse counts top-level monitored systems such as Docker hosts, Kubernetes clusters, Proxmox nodes, standalone hosts, and TrueNAS systems. Compare self-hosted plans in Pulse Account and return here with Pulse Pro activated automatically.",
|
||||
),
|
||||
).toBeVisible();
|
||||
await expect(page.getByRole("button", { name: "Hide counting rules" })).toBeVisible();
|
||||
await expect(
|
||||
page.getByText(
|
||||
"A monitored system is a top-level monitored root such as a Docker host, Kubernetes cluster, Proxmox node, standalone host, or TrueNAS system. Each root counts once no matter how Pulse collects it. Child resources like VMs, containers, pods, disks, backups, and services underneath that root are included.",
|
||||
),
|
||||
).toBeVisible();
|
||||
}
|
||||
|
||||
test.describe("Self-hosted upgrade return flow", () => {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue