Unit D30-U03 · Software engineering and reproducible delivery
Tests, mocks, and integration checks
Test expected, malformed, and unavailable-service cases.
Outline only
This is an outline, not a lesson yet
The full lesson for this unit has not been written. This page shows what it is planned to teach, how long it is planned to take, and the reading chosen to support it. No explanation, worked example, quiz or task is published for it yet. See content status.
Planned outcome
Test expected, malformed, and unavailable-service cases.
How it would be assessed
Assessed outcome: Test expected, malformed, and unavailable-service cases.
Evidence: A task artifact demonstrating the stated action, a verification or comparison record, and a short explanation of uncertainty or failure. Use a new input for the completion check. Allocate the scheduled time across reading, demonstration, lab, quiz, and feedback rather than treating it as reading alone.
Planned time and place
- Planned time
- 5 h in total, including practice and assessment (a planning figure, not tested with learners)
- Module
- D30: Software engineering and reproducible delivery
- Chapter
- D30-C02: Testing and collaborative change
- Prerequisite modules
- D10
- Used in programs
- P06, P07
Selected reading for this topic
Core reading
- pytest getting started Assertions, fixtures, and small reproducible checks.Try it: Test expected, malformed, and unavailable-service cases.About this reference (W12)
Hands-on
- FastAPI Inspect API schema, validation, and application tests.Try it: Test expected, malformed, and unavailable-service cases.About this reference (G14)
Reading is chosen to support the outcome; none of it is compulsory homework. Links go to the owners' own sites and some resources cost money. Reviewed 2026-11-17.