ThePhaselessandClaude Opus 5 11d7e59263 test: assert what the challenge tests claim to assert ...

Three tests checked solution.status against HTTPStatus.OK, which the
endpoint now hardcodes, so the check could never fail. Drop it everywhere
except the test that exists to pin that behaviour.

That left the self-clearing case asserting only that nothing raised, which
the click test already covers. Give it a measurable widget and assert we
never press it: a challenge that clears on its own is the one case where
touching the checkbox would be wrong, and nothing tested it. Verified by
moving the click ahead of the exit check, which the assertion now catches.

Drop the fake page.evaluate return as well, since /v1 stopped calling it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-18 04:00:17 +02:00

..

__init__.py

swtich to dummy test

2024-07-24 20:42:23 +00:00

main_test.py

test: assert what the challenge tests claim to assert

2026-08-18 04:00:17 +02:00

owui_test.py

refactor: drop the solver and prove the challenge page is gone

2026-08-18 02:45:19 +02:00