What the developer wrote
Authored by Nicolas Dorier
Fix flaky test
What changed, and why it matters
This commit adds a single line to a test file, instructing an automated browser test to wait for an alert message before continuing. It is purely a test stability fix and does not change any production code, user-facing behavior, or security controls.
No security action needed. Treat as routine test maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In BTCPayServer.Tests/PlaywrightTests.cs, after filling a description field and clicking the primary button, the test now calls await s.FindAlertMessage(); before waiting for a new page to open. This is a synchronization fix to address a flaky Playwright UI test; it has no effect on the BTCPay Server application code.
Changed components
BTCPayServer.Tests/PlaywrightTests.csInspect captured patch +1 / −0
diff --git a/BTCPayServer.Tests/PlaywrightTests.cs b/BTCPayServer.Tests/PlaywrightTests.cs
index 420fac2..feabe41 100644
--- a/BTCPayServer.Tests/PlaywrightTests.cs
+++ b/BTCPayServer.Tests/PlaywrightTests.cs
@@ -1853,6 +1853,7 @@ namespace BTCPayServer.Tests
var description = s.Page.Locator(".card-block");
await description.FillAsync("Description Edit");
await s.ClickPagePrimary();
+ await s.FindAlertMessage();
opening = s.Page.Context.WaitForPageAsync();
await s.Page.ClickAsync("text=View");
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.