The Life Starter
0 of 6 complete0%
Course Library · Lesson 6 of 6
Digital · Guided lesson

Test and explain the object model

About 26 minutes · 4 reading + 22 practice and checks
Time includes reading, practice, and questions. Extra videos or further study are optional.
See this course’s project requirements

An original library-room booking simulation using independent objects, invariants, composition and an event history.

Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.

What to include

  • A room-state contract with 10:00 mapped to 3.
  • An independent-instance check with unchanged B.
  • A rejection record with unchanged booking state.
  • A composed booking trace with no event for an unknown room.
  • A composition design note with responsibility boundaries.
  • A tested booking model with independent state and honest rejection evidence.

Review and revise

Use these criteria to check your work and choose what to improve.

  • The implementation or declared simulation follows the supplied contract and retains inspectable original inputs.
  • Normal, boundary and rejected cases are recorded with expected versus observed results.
  • The changed case has a correct explanation and does not rely on hidden state.
  • The project includes source, outputs, instructions and honest tool, privacy and verification limits.
Open the full course project
Want more background?
Before you begin

The idea in everyday life

Run objects.py, then add a successful B booking at 11:00 for 6 people and retry it.

The idea

Test both outcomes and preserved state. A rejection should not append a completion event, corrupt another room or change a valid earlier booking.

Follow along

Test and explain the object model — original worked practice

Test both outcomes and preserved state. A rejection should not append a completion event, corrupt another room or change a valid earlier booking.

Run objects.py, then add a successful B booking at 11:00 for 6 people and retry it.

  1. 1. Step 1

    Run the five supplied checks.

    You should see: Baseline object checks pass.

    This keeps the rule and its observable result together.

  2. 2. Step 2

    Add the capacity-boundary B booking.

    You should see: B gains 11:00→6 and events reaches 2.

    This keeps the rule and its observable result together.

  3. 3. Step 3

    Retry B’s same slot and inspect state.

    You should see: The retry fails; B and event count stay unchanged.

    This keeps the rule and its observable result together.

  4. 4. Step 4

    Package the object diagram, code and state test table.

    You should see: A tested booking model with independent state and honest rejection evidence.

    This keeps the rule and its observable result together.

Now change one thing

Two successful bookings exist; three invalid attempts follow. Enter final event count.

Your work

What to finish

A tested booking model with independent state and honest rejection evidence.

Common mistake

Watch for this

Testing only returned messages rather than checking that rejected operations leave all owned state unchanged.

How can I tell I understand it?

Explain and demonstrate the required distinction: Test both outcomes and preserved state. A rejection should not append a completion event, corrupt another room or change a valid earlier booking. Show a changed input and the expected result without weakening this contract.

Try 3 questions

Quick knowledge check

Answer all 3 questions. Get at least 2 right and the lesson completes automatically.

Not yet passed

You’ll get an explanation for each answer. Signed in? Your results save to your account.

1Which test exposes shared mutable state?
2Which evidence checks safe failure?
3What belongs in this handoff?
0 of 3 answeredApply the lesson to a short question, then review the explanation.
6
Finish this lesson

Pass the check. We’ll save the progress.

Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.

Go to the knowledge check
Tools, templates, and lesson sources

Tools and templates

Tools open in a new tab so you can keep your place here.

Sources and further reading

Explore the references behind this lesson.

docs.python.org — unittest.html
Source & access notes · checked 2026-10-01

Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.

Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.

Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.

Report a problem with this lesson

Tell us what went wrong. Please leave out personal information and private project contents.

No sign-in needed.