justin
3221f7abe8
CI / check (pull_request) Successful in 7s
Most current systems (default Debian/Ubuntu, recent macOS) install Python only as `python3`, with no bare `python` on PATH, so learners who copied `python cli.py ...` into their host shell hit "command not found". Convert host-shell `python <cmd>` -> `python3 <cmd>` across module/lab READMEs, lab `.py` docstrings & usage strings, blog posts, lab prompt and instruction files, the M04 verify.sh message, and the M10/M24 lab patches. Module 01's convention note (and its blog/02 mirror) is rewritten so `python3` is canonical and `python` is the documented fallback. Stop-lines respected: Docker image tags (`python:3.12-slim`), `.venv/.../python` and `...\.venv\Scripts\python.exe` paths, the M20 `"command": "python"` teaching example and surrounding venv prose, container-internal invocations (M16/M18 Dockerfiles, M16 README `docker run` examples), and CI-workflow `run:` steps fed by `actions/setup-python` / `image: python:3.12` are left as `python` on purpose. pip was left out of scope: most occurrences are prose or CI/container-internal, and `pip3` does not fix the PEP 668 externally-managed-environment refusal that the course already addresses with venvs. The M01 note is worded to stay consistent with bare `pip` (use whichever pip pairs with your Python). Build (tools/build_wiki.py) and tools/check.sh both pass. Closes #104 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GAEzanEoGJT5o1VizQar47
77 lines
2.4 KiB
Python
77 lines
2.4 KiB
Python
"""Reference test suite for the Module 13 lab. Peek only after you've tried it yourself.
|
|
|
|
Named `reference_test_tasks.py` (not `test_*.py`) on purpose, so `python3 -m unittest discover`
|
|
does NOT pick it up automatically. To run it, copy it next to your working `tasks.py` (e.g.
|
|
`~/ai-workflow-course/work/tasks-app/`) and run, from that directory:
|
|
|
|
python3 -m unittest reference_test_tasks
|
|
|
|
It assumes `tasks.py` is importable, which is why you run it from the tasks-app directory.
|
|
|
|
The point of this file is to show the difference between a test that asserts CURRENT BEHAVIOR
|
|
(a tautology that passes against the bug) and a test that encodes INTENT (and fails until the
|
|
bug is fixed).
|
|
"""
|
|
|
|
import unittest
|
|
|
|
from tasks import TaskList
|
|
|
|
|
|
class TestTaskBasics(unittest.TestCase):
|
|
def test_add_appends_a_task(self):
|
|
tl = TaskList()
|
|
tl.add("write the tests")
|
|
self.assertEqual(len(tl.tasks), 1)
|
|
self.assertEqual(tl.tasks[0].title, "write the tests")
|
|
self.assertFalse(tl.tasks[0].done)
|
|
|
|
def test_complete_marks_done(self):
|
|
tl = TaskList()
|
|
tl.add("a")
|
|
tl.complete(0)
|
|
self.assertTrue(tl.tasks[0].done)
|
|
|
|
def test_pending_excludes_completed(self):
|
|
tl = TaskList()
|
|
tl.add("a")
|
|
tl.add("b")
|
|
tl.complete(0)
|
|
self.assertEqual([t.title for t in tl.pending()], ["b"])
|
|
|
|
|
|
class TestPendingCount(unittest.TestCase):
|
|
def test_count_with_nothing_done_is_a_tautology(self):
|
|
# This passes even with the bug, because when nothing is completed
|
|
# "total" and "pending" are the same number. It proves almost nothing.
|
|
tl = TaskList()
|
|
tl.add("a")
|
|
tl.add("b")
|
|
self.assertEqual(tl.pending_count(), 2)
|
|
|
|
def test_count_reflects_intent_after_completing_one(self):
|
|
# This encodes what `count` is FOR: how many tasks are still pending.
|
|
# It FAILS against the planted bug (pending_count returns len(self.tasks)),
|
|
# and passes once pending_count returns len(self.pending()).
|
|
tl = TaskList()
|
|
tl.add("a")
|
|
tl.add("b")
|
|
tl.complete(0)
|
|
self.assertEqual(tl.pending_count(), 1)
|
|
|
|
def test_count_of_all_done_is_zero(self):
|
|
tl = TaskList()
|
|
tl.add("a")
|
|
tl.complete(0)
|
|
self.assertEqual(tl.pending_count(), 0)
|
|
|
|
|
|
# The fix, for reference:
|
|
#
|
|
# def pending_count(self) -> int:
|
|
# return len(self.pending())
|
|
|
|
|
|
if __name__ == "__main__":
|
|
unittest.main()
|