status.ffig.ar

reminders

End-to-end behaviour tests, driven against the public site in a real browser by the integration service. self-tests passing (last 24h)

Test plan — v2 · weekly habits lifecycle

Each cell is a scheduled run; times are wall-clock in the service's timezone. Expand a scenario for its exact steps; the square is its latest result. The table is generated from the running test code and cannot drift from what executes.

sunmontuewedthufrisat
setup
  1. log in as test user (real Auth0)
  2. editor starts empty
  3. create 'Drink water'
  4. create 'Stretch'
  5. api shows both habits pending
  6. home shows both buttons
00:00
morning
  1. log in as test user (real Auth0)
  2. all habits pending in api
  3. buttons shown on load
  4. pressing every button empties the list
  5. 'done for today' shown
  6. all habits off in api
09:0009:0009:0009:0009:0009:0009:00
afternoon
  1. log in as test user (real Auth0)
  2. home loads
  3. no buttons shown
  4. 'done for today' shown
  5. all habits off in api
15:0015:0015:0015:0015:0015:0015:00
midweek
  1. log in as test user (real Auth0)
  2. editor shows two habits
  3. remove the oldest habit
  4. create 'Read a page'
  5. api shows the new habit pending
  6. home shows exactly the new habit's button
16:00

setup is chained right after the weekly test-user rotation.

Historic

One row per day, one column per scenario, newest first. A release note marks each revision of the suite: the columns above it are the current tests, the columns below are what ran before. Select a day for its runs, a scenario for its steps. Runs are retained for one year.

setupmorningafternoonmidweek
2026-08-13··
2026-08-12·
2026-08-11··
2026-08-10··
2026-08-09·
2026-08-08··
2026-08-07··
2026-08-06··
2026-08-05·
2026-08-04··
2026-08-03··
2026-08-02·
2026-08-01··
2026-07-31··
2026-07-30··
2026-07-29·
2026-07-28··
2026-07-27··
2026-07-26·
2026-07-25··
2026-07-24··
2026-07-23··
2026-07-22·
2026-07-21··
2026-07-20··
2026-07-19·
2026-07-18··
2026-07-17··
2026-07-16··
2026-07-15·
2026-07-14··
2026-07-13··
2026-07-12·
2026-07-11··
v2 · weekly habits lifecycle
since 2026-07-11 · commit e76db4f

Users now create their own daily habits, so the tests follow a whole week of one user's life: Sunday's fresh test user creates two habits through the editor, every morning presses each pending button, every afternoon confirms they stayed done, and Wednesday swaps one habit mid-week. Every scenario logs in through the real Auth0 page and cross-checks the UI against the API.

morningafternoon
2026-07-11
2026-07-10
2026-07-09
2026-07-08
2026-07-07
2026-07-06
2026-07-05
2026-07-04
2026-07-03
2026-07-02
2026-07-01
2026-06-30
2026-06-29
2026-06-28
2026-06-27
2026-06-26
2026-06-25
2026-06-24
2026-06-23
2026-06-22
2026-06-21
2026-06-20
2026-06-19
2026-06-18
2026-06-17
2026-06-16
v1 · single bit per user
since 2026-06-15 · commit 3733a9a

Each user had a single on/off habit bit and the home showed one button. Two daily scenarios: morning observed the bit on (the midnight job reset it), pressed the button and saw the bit turn off; afternoon confirmed it stayed off. Same real-Auth0 login and UI-vs-API cross-checks as today.