What the developer wrote
Authored by Nicolas Dorier
Fix test
What changed, and why it matters
This is a one-line change to a test file. It adjusts an assertion so that the test now expects a database-migrated API key to have a null CreatedAt value instead of a non-null value. There is no production code change and no security relevance visible in the commit.
No security action required. Review as normal test maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In BTCPayServer.Tests/DatabaseTests.cs, the assertion Assert.NotNull(migratedApiKey.CreatedAt) was changed to Assert.Null(migratedApiKey.CreatedAt). This is purely a test expectation update, likely aligning the test with a prior schema or migration behavior change. No application logic, authentication, authorization, cryptography, input handling, or network code is modified.
Changed components
BTCPayServer.Tests/DatabaseTests.csInspect captured patch +1 / −1
### BTCPayServer.Tests/DatabaseTests.cs
@@ -348,7 +348,7 @@ await ctx.Database.GetDbConnection().ExecuteAsync("""
Assert.Equal(expectedHash, migratedApiKey.Hash);
Assert.Equal("2683fe", migratedApiKey.Prefix);
Assert.Null(migratedApiKey.Key);
- Assert.NotNull(migratedApiKey.CreatedAt);
+ Assert.Null(migratedApiKey.CreatedAt);
var usage = await ctx.ApiKeyPermissionUsages.SingleAsync();
Assert.Equal(expectedApiKeyId, usage.ApiKeyId);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.