You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test(lua): cover challenge routes in start endpoint
Extend tests/lua/endpoints/test_start.py with a TestStartChallenge
class covering the new challenge branch. No new fixtures: challenges
start from MENU like the existing start tests, and the wrong-state case
reuses the existing start/state-BLIND_SELECT fixture. fixtures.json is
unchanged.
- happy_path (parametrized c_omelette_1, c_jokerless_1, c_mad_world_1):
lands in BLIND_SELECT with deck=b_challenge, stake=stake_white, and
the challenge id echoed in the gamestate.
- with_seed: proves challenge composes freely with seed.
- effect_applied (deep): The Omelette starts with 5 Eggs — asserts the
challenge actually took effect, not just the flag.
- conflict_with_deck / _stake / _both: BAD_REQUEST "cannot be combined".
- invalid_id: BAD_REQUEST "Expected a c_* challenge id".
- wrong_type: schema-level BAD_REQUEST "must be of type string".
The existing TestStartEndpoint / validation / state-requirement tests
stay green unchanged — they are the regression guard for the normal
path (deck/stake are now schema-optional, enforced in execute with the
same verbatim error strings).
0 commit comments