mardausdennis 15782d1836 tell absence and a slow render apart when a task fails ...

Every failed task printed the same reason, because the blanket catch in
complete_all_tasks treated NoSuchElementException and TimeoutException as one
finding. A wait that expires says nothing about whether the section was there,
since wait_for_element swallowed whatever the getter raised and returned False.
A market that does not ship visual search and a points panel that was on screen
and slow both arrived as TimeoutException

wait_for_element now keeps the last reason the getter gave and raises
ElementNeverAppeared when nothing was in the DOM for the whole wait.
_container_by_id raises ElementNotReady when the id is present but no visible
copy has content yet, which is the hydrating case it used to report as missing.
Both subclass what they refine, so claim_bonus_points and
complete_bing_daily_set keep working untouched

A task that was reached and then ran out of time is now a [FAIL] rather than a
[SKIP], because it may have left points behind. Absence stays a [SKIP]

56 tests pass, 20 of them new. A mutation check backs them, forcing every
expired wait to count as absence fails 2, and collapsing the two branches back
into one [SKIP] fails 4

Refs #52

2026-09-03 22:38:01 +02:00

..

fakes.py

add tests for the selector logic that keeps breaking

2026-08-28 11:08:17 +02:00

test_element_selectors.py

tell absence and a slow render apart when a task fails

2026-09-03 22:38:01 +02:00

test_multi_account.py

match the unittest convention the selector tests introduced

2026-08-29 14:36:08 -07:00

test_task_outcomes.py

tell absence and a slow render apart when a task fails

2026-09-03 22:38:01 +02:00