DeleteSepaMandate
Tests
| Test |
Duration |
Result |
| bankAccountAdminUser_canNotDeleteRelatedSepaMandate() |
1.279s |
passed |
| globalAdmin_canDeleteArbitrarySepaMandate() |
1.253s |
passed |
| normalUser_canNotDeleteUnrelatedSepaMandate() |
1.392s |
passed |
Standard output
ContextBasedTestWithCleanup.retrieveInitialTestData
normalUser_canNotDeleteUnrelatedSepaMandate(): TOTAL OBJECT COUNT (initial): 210 -> 210
nothing deleted
ContextBasedTestWithCleanup.cleanupAndCheckCleanup
normalUser_canNotDeleteUnrelatedSepaMandate(): TOTAL OBJECT COUNT (after): 210 -> 210
ContextBasedTestWithCleanup.retrieveInitialTestData
globalAdmin_canDeleteArbitrarySepaMandate(): TOTAL OBJECT COUNT (initial): 210 -> 210
nothing deleted
nothing deleted
ContextBasedTestWithCleanup.cleanupAndCheckCleanup
globalAdmin_canDeleteArbitrarySepaMandate(): TOTAL OBJECT COUNT (after): 210 -> 210
ContextBasedTestWithCleanup.retrieveInitialTestData
bankAccountAdminUser_canNotDeleteRelatedSepaMandate(): TOTAL OBJECT COUNT (initial): 210 -> 210
nothing deleted
2026-08-10T15:06:26.377Z WARN 371 --- [o-auto-1-exec-2] o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 0, SQLState: P0001
2026-08-10T15:06:26.378Z ERROR 371 --- [o-auto-1-exec-2] o.h.engine.jdbc.spi.SqlExceptionHelper : ERROR: [403] Subject {784193d8-30b4-5f2f-ba0e-bc34a6e1108b} is not allowed to delete hs_office.sepamandate uuid 26cccff1-969b-4ac7-a596-f83191bb491b
Where: PL/pgSQL function hs_office.sepamandate_instead_of_delete_tf() line 7 at RAISE
{
"timestamp": "2026-08-10 03:06:26",
"path": "",
"statusCode": 403,
"statusPhrase": "Forbidden",
"message": "ERROR: [403] Subject {784193d8-30b4-5f2f-ba0e-bc34a6e1108b} is not allowed to delete hs_office.sepamandate uuid 26cccff1-969b-4ac7-a596-f83191bb491b"
}
ContextBasedTestWithCleanup.cleanupAndCheckCleanup
bankAccountAdminUser_canNotDeleteRelatedSepaMandate(): TOTAL OBJECT COUNT (after): 210 -> 210