What changed, and why it matters
This commit only changes a test file. It adds one extra assertion and reorders two existing assertions. There is no change to production code, no security fix, and no vulnerability.
No security action needed. Treat as a routine test maintenance commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies BTCPayServer.Tests/UnitTest1.cs. It adds Assert.Null(rescan.PreviousError); and swaps the order of Assert.NotNull(rescan.RemainingTime); and Assert.NotNull(rescan.Progress);. This is purely a test-logging/test-coverage change within an existing test loop. No application code is touched.
Changed components
BTCPayServer.Tests/UnitTest1.csInspect captured patch +2 / −1
diff --git a/BTCPayServer.Tests/UnitTest1.cs b/BTCPayServer.Tests/UnitTest1.cs
index c75d9aa..d81d87a 100644
--- a/BTCPayServer.Tests/UnitTest1.cs
+++ b/BTCPayServer.Tests/UnitTest1.cs
@@ -585,9 +585,10 @@ namespace BTCPayServer.Tests
}
else
{
+ Assert.Null(rescan.PreviousError);
Assert.Null(rescan.TimeOfScan);
- Assert.NotNull(rescan.RemainingTime);
Assert.NotNull(rescan.Progress);
+ Assert.NotNull(rescan.RemainingTime);
Thread.Sleep(100);
}
}
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.