aboutsummaryrefslogtreecommitdiff
path: root/tests/test-pearl-delete.el
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-24 15:01:01 -0500
committerCraig Jennings <c@cjennings.net>2026-05-24 15:01:01 -0500
commit1a26149d4d7f16adb1552ba31a2de290a5c86fc4 (patch)
treeb61b23fd96ee757e6cc04020532c0717d20b102f /tests/test-pearl-delete.el
parent44b7e8e42383a0e2c7024f250c2d16de6b66c652 (diff)
downloadpearl-1a26149d4d7f16adb1552ba31a2de290a5c86fc4.tar.gz
pearl-1a26149d4d7f16adb1552ba31a2de290a5c86fc4.zip
test: cover sync-back push-failure branches at the command level
Added ERT tests that the three sync commands leave provenance untouched when the push fails (:success nil): pearl-sync-current-issue keeps LINEAR-DESC-SHA256 and -UPDATED-AT, pearl-sync-current-issue-title keeps LINEAR-TITLE-SHA256, and pearl-edit-current-comment keeps LINEAR-COMMENT-SHA256 — and in each case the edited text stays in the buffer for retry. Each test asserts the push was attempted with the rendered text. The commands already behave correctly; this locks it. 360 tests green.
Diffstat (limited to 'tests/test-pearl-delete.el')
0 files changed, 0 insertions, 0 deletions