Confirmed users
360
edits
No edit summary |
|||
Line 113: | Line 113: | ||
| Connection loss recovery | | Connection loss recovery | ||
| We need tests for connection loss during various points and the logic that makes those tests pass. Sync, mutation (no mutations dispatched), mutation (mutations dispatched). | | We need tests for connection loss during various points and the logic that makes those tests pass. Sync, mutation (no mutations dispatched), mutation (mutations dispatched). | ||
| | | 2 days | ||
|- | |||
| Adaptive sync improvements, no tests | |||
| Be smarter about how many days we ask for at a time, don't try and look for messages before the internet was invented, etc. No automated tests for time reasons, but manual verification run and dogfooding will make failures obvious. | |||
| 0.75 days | |||
| done | |||
|- | |||
| Adaptive sync unit tests | |||
| Unit tests for the prior deal. These will need to go in the overload test case buckets because we will need to produce a lot of messages for realistic tests. | |||
| 1.25 days | |||
|- | |- | ||
! Accounts | ! Accounts | ||
Line 189: | Line 198: | ||
| | | | ||
| 2 days | | 2 days | ||
| done | |||
|- | |- | ||
| message flag mutation UI hookup | | message flag mutation UI hookup | ||
| single and batch mutations from the message list, single mutation from the reader. | | single and batch mutations from the message list, single mutation from the reader. | ||
| 1 day | | 1 day | ||
| 50% (single mutation only) | |||
|- | |- | ||
| message moves (same account) and deletion: offline persisted, undo, no UI, tests | | message moves (same account) and deletion: offline persisted, undo, no UI, tests |