What the developer wrote
Authored by Nicolas Dorier
Try fix flaky
What changed, and why it matters
This commit only changes the order of steps in an automated test script for the BTCPay Server project. It moves a 'Description Edit' step earlier in the test flow to try to fix a flaky (unreliable) test. There is no change to production code, no user-facing behavior change, and no security relevance.
No security action needed. This is a routine test maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies BTCPayServer.Tests/PlaywrightTests.cs, a Playwright UI test. It reorders two test actions: filling the ‘.note-editable’ description field and clicking the primary button now happen before clicking on ‘PP1’ and editing the ‘#Name’ field. This is a test reliability fix only; no application code is changed.
Changed components
BTCPayServer.Tests/PlaywrightTests.csInspect captured patch +4 / −2
diff --git a/BTCPayServer.Tests/PlaywrightTests.cs b/BTCPayServer.Tests/PlaywrightTests.cs
index 78337c5..0e42a1d 100644
--- a/BTCPayServer.Tests/PlaywrightTests.cs
+++ b/BTCPayServer.Tests/PlaywrightTests.cs
@@ -1854,12 +1854,14 @@ namespace BTCPayServer.Tests
await s.GoToStore(s.StoreId, StoreNavPages.PullPayments);
+ await s.Page.FillAsync(".note-editable", "Description Edit");
+ await s.ClickPagePrimary();
+
await s.Page.ClickAsync("text=PP1");
var name = s.Page.Locator("#Name");
await name.ClearAsync();
await name.FillAsync("PP1 Edited");
- await s.Page.FillAsync(".note-editable", "Description Edit");
- await s.ClickPagePrimary();
+
await s.FindAlertMessage();
opening = s.Page.Context.WaitForPageAsync();
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.