chore(test): подтвердить обработку ошибок сохранения отправки
This commit is contained in:
1 parent
d44511da8e
commit
507c7010ad
6 files changed
+104
-4
No files matched your search
@@ -0,0 +1,60 @@
|
||||
{
|
||||
"date": "2026-10-08",
|
||||
"backendSource": "8782054",
|
||||
"database": "mmapp_acceptance_20261007",
|
||||
"cases": [
|
||||
{
|
||||
"case": "history-insert-failure",
|
||||
"result": {
|
||||
"sent": 1,
|
||||
"failed": 0,
|
||||
"held": 1,
|
||||
"errors": [
|
||||
"outbox acceptance-claim-1791442930116: Telegram API принял сообщение, но запись результата в БД не подтверждена"
|
||||
]
|
||||
},
|
||||
"saved": {
|
||||
"id": "acceptance-claim-1791442930116",
|
||||
"status": "unknown",
|
||||
"retry_count": 0,
|
||||
"resolution_version": 0
|
||||
},
|
||||
"historyRows": 0,
|
||||
"senderCalls": 1,
|
||||
"noAutomaticRetry": true
|
||||
},
|
||||
{
|
||||
"case": "commit-acknowledgement-loss",
|
||||
"result": {
|
||||
"sent": 1,
|
||||
"failed": 0,
|
||||
"held": 1,
|
||||
"errors": [
|
||||
"outbox acceptance-claim-1791442930116: Telegram API принял сообщение, но запись результата в БД не подтверждена. Сохранение статуса не подтверждено; processing не повторяется автоматически"
|
||||
]
|
||||
},
|
||||
"saved": {
|
||||
"id": "acceptance-claim-1791442930116",
|
||||
"status": "sent",
|
||||
"retry_count": 0,
|
||||
"resolution_version": 1
|
||||
},
|
||||
"history": [
|
||||
{
|
||||
"id": "acceptance-claim-1791442930116-history",
|
||||
"sent_ok": true
|
||||
}
|
||||
],
|
||||
"injectedAfterRealCommit": true,
|
||||
"noFalseUnknownOverwrite": true,
|
||||
"noAutomaticRetry": true
|
||||
}
|
||||
],
|
||||
"interceptedSenderCalls": 2,
|
||||
"realExternalMessages": 0,
|
||||
"limits": [
|
||||
"Telegram response intercepted in-process; no actual delivery claim",
|
||||
"SQL history failure real trigger; COMMIT ack fault injected at node-pg boundary after actual COMMIT",
|
||||
"Single test process, no physical network-disconnect or multi-instance proof"
|
||||
]
|
||||
}
|
||||
Reference in new issue
Block a user