forked from Blendman974/faceclaw
30 lines
1.8 KiB
Markdown
30 lines
1.8 KiB
Markdown
# Android calendar selection validation
|
|
|
|
Software: `npm test` and `bash lint.sh` for changed TypeScript files.
|
|
`tests/calendar-selection.test.cjs` covers preference reloads, all versus none,
|
|
duplicate names/accounts, selection changes with cached readers, deleted IDs,
|
|
recurrence occurrences and forwarding the selection to the provider before its
|
|
limit. Provider SQL structure is checked statically; the mocked bridge does not
|
|
replace an Android CalendarContract integration test.
|
|
|
|
On an Android device (pending):
|
|
|
|
1. With no saved preference, compare events with the current release.
|
|
2. Open Calendar's window menu > Calendars displayed (also available through
|
|
Glanceboard's Calendar widget settings). Select between two equal-named
|
|
calendars belonging to different accounts. Check ID/account labels.
|
|
3. Create more than 50 early events in an excluded calendar and later recurring
|
|
events in a selected calendar. Check those later occurrences still appear.
|
|
4. Select “No calendars”: Calendar, Glanceboard and any other readers must be
|
|
empty immediately. Restart and confirm the selection persists.
|
|
5. Select individual calendars, rename one, then delete one. Remaining selections
|
|
must stay unchanged. A missing selected ID is shown as unavailable and may be
|
|
removed; it never causes a fallback to all calendars.
|
|
6. Select “All calendars”, add a calendar, and check it is included. In individual
|
|
mode, newly added calendars stay excluded. Check all-day and timed recurring
|
|
events in both Calendar and Glanceboard, including timezone/DST boundaries.
|
|
|
|
IDs are Android CalendarContract IDs, stable across display-name changes within
|
|
an installation. Removing/re-adding an account can create new calendar IDs.
|
|
The iOS calendar reader and its behavior are unchanged; iOS selection is deferred.
|