Fix: test_backlog_sort_order setzt beide sort_order-Werte ohne Tie.
Deploy Development / deploy (push) Successful in 44s
Test Suite / pytest-backend (push) Successful in 1m49s
Test Suite / lint-backend (push) Successful in 2s
Test Suite / compose-smoke (push) Has been skipped
Test Suite / k6 /api/health Baseline (push) Successful in 19s
Test Suite / playwright-smoke (push) Successful in 12s
Deploy Development / deploy (push) Successful in 44s
Test Suite / pytest-backend (push) Successful in 1m49s
Test Suite / lint-backend (push) Successful in 2s
Test Suite / compose-smoke (push) Has been skipped
Test Suite / k6 /api/health Baseline (push) Successful in 19s
Test Suite / playwright-smoke (push) Successful in 12s
Einzel-PATCH auf 0 kollidierte mit dem ersten Item; entspricht dem Batch-Reorder aus AP1.12c. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
1 parent
4f2f801889
commit
495993cad6
2 files changed
+8
-1
No files matched your search
@@ -255,6 +255,13 @@ def test_backlog_sort_order(client):
|
||||
second = _create_backlog(client, token, initiative_id, title="Second").json()
|
||||
assert first["sort_order"] < second["sort_order"]
|
||||
|
||||
# Reorder wie im Frontend: beide Geschwister sort_order neu setzen (kein Tie)
|
||||
bumped = client.patch(
|
||||
f"/api/backlog/{first['id']}",
|
||||
json={"sort_order": 10},
|
||||
headers=_auth(token),
|
||||
)
|
||||
assert bumped.status_code == 200
|
||||
patched = client.patch(
|
||||
f"/api/backlog/{second['id']}",
|
||||
json={"sort_order": 0},
|
||||
|
||||
+1
-1
@@ -1,3 +1,3 @@
|
||||
APP_VERSION = "0.16.8-ap1.12d"
|
||||
APP_VERSION = "0.16.9-ap1.12d-fix"
|
||||
DB_SCHEMA_VERSION = "015"
|
||||
APP_NAME = "jinkendo-kairo"
|
||||
Reference in new issue
Block a user