Julian Tabel
4aae12cd72
46 tests across 12 schema classes covering CamelModel alias generation, required field validation, optional field defaults, camelCase input/output, nested model coercion, and from_attributes support. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
title, status, type, priority, created_at, updated_at, parent
| title | status | type | priority | created_at | updated_at | parent |
|---|---|---|---|---|---|---|
| Unit tests for Pydantic schemas and model validation | completed | task | normal | 2026-02-10T09:33:03Z | 2026-02-21T11:39:58Z | nuzlocke-tracker-yzpb |
Write unit tests for the Pydantic schemas in backend/src/app/schemas/. These are pure validation logic and can be tested without a database.
Checklist
- Test
CamelModelbase class (snake_case → camelCase alias generation) - Test run schemas — creation validation, required fields, optional fields, serialization
- Test game schemas — validation rules, field constraints
- Test encounter schemas — status enum validation, field dependencies
- Test boss schemas — nested model validation
- Test genlocke schemas — complex nested structures
- Test evolution schemas — validation of evolution chain data
- Test Pokemon create schema (types list, required fields)
Notes
- Focus on: valid input acceptance, invalid input rejection, serialization output format
- The
CamelModelbase class does alias generation — verify both input (camelCase) and output (camelCase) work - Test edge cases like empty strings, negative numbers, missing required fields