This commit was merged in pull request #105.
This commit is contained in:
@@ -24,7 +24,7 @@ Ask for these if they weren't given:
|
||||
|
||||
- Core logic lives in `tasks.py` (the `TaskList` class). The CLI front end is `cli.py`. State
|
||||
persists to `tasks.json`. **Never edit `tasks.json` by hand; it's generated.**
|
||||
- Tests live in `test_tasks.py` and run with `python -m unittest`. Standard library only; no
|
||||
- Tests live in `test_tasks.py` and run with `python3 -m unittest`. Standard library only; no
|
||||
third-party packages, no new dependencies.
|
||||
- The human-facing change log is `CHANGELOG.md`, newest entry on top.
|
||||
|
||||
@@ -42,10 +42,10 @@ Ask for these if they weren't given:
|
||||
crash." Assert the end state (e.g. after `clear()`, `len(tasks) == 0` and `pending()` is empty).
|
||||
A test that passes against a broken implementation is worse than no test.
|
||||
|
||||
4. **Run the tests.** `python -m unittest` from the project root. Do not claim success until it's
|
||||
4. **Run the tests.** `python3 -m unittest` from the project root. Do not claim success until it's
|
||||
green. If it fails, fix the code, not the test, and run again.
|
||||
|
||||
5. **Smoke-test the CLI.** Actually run it: `python cli.py COMMAND_NAME`, then `python cli.py list`
|
||||
5. **Smoke-test the CLI.** Actually run it: `python3 cli.py COMMAND_NAME`, then `python3 cli.py list`
|
||||
to confirm the visible result. Paste what you ran and what it printed.
|
||||
|
||||
6. **Add a `CHANGELOG.md` entry.** One line under the top heading, present tense:
|
||||
@@ -57,8 +57,8 @@ Ask for these if they weren't given:
|
||||
|
||||
## Done when
|
||||
|
||||
- `python -m unittest` is green and includes a new test that actually exercises `COMMAND_NAME`.
|
||||
- `python cli.py COMMAND_NAME` does `WHAT_IT_DOES` and you've shown the output.
|
||||
- `python3 -m unittest` is green and includes a new test that actually exercises `COMMAND_NAME`.
|
||||
- `python3 cli.py COMMAND_NAME` does `WHAT_IT_DOES` and you've shown the output.
|
||||
- `CHANGELOG.md` has a new top line for the command.
|
||||
- One commit contains the code, the test, and the changelog line, and nothing else (no
|
||||
`tasks.json`, no unrelated reformatting).
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
"""Tiny command-line front end for the demo task app.
|
||||
|
||||
Run it:
|
||||
python cli.py add "write the lesson"
|
||||
python cli.py list
|
||||
python cli.py count
|
||||
python3 cli.py add "write the lesson"
|
||||
python3 cli.py list
|
||||
python3 cli.py count
|
||||
|
||||
State is kept in tasks.json next to this file. The same minimal app from Module 1 onward; the
|
||||
target your "add a command" skill extends.
|
||||
@@ -32,7 +32,7 @@ def save(tlist: TaskList) -> None:
|
||||
def main(argv: list[str]) -> int:
|
||||
tlist = load()
|
||||
if not argv:
|
||||
print("usage: python cli.py [add <title> | list | done <index> | count]")
|
||||
print("usage: python3 cli.py [add <title> | list | done <index> | count]")
|
||||
return 1
|
||||
|
||||
command = argv[0]
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
"""Test suite for the tasks-app. Run from this folder with:
|
||||
|
||||
python -m unittest
|
||||
python3 -m unittest
|
||||
|
||||
Your "add a command" skill should ADD a test here for every new command. The point is to assert
|
||||
intended behavior, not just that nothing crashed.
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
"""Tiny command-line front end for the demo task app.
|
||||
|
||||
Run it:
|
||||
python cli.py add "write the lesson"
|
||||
python cli.py list
|
||||
python cli.py count
|
||||
python3 cli.py add "write the lesson"
|
||||
python3 cli.py list
|
||||
python3 cli.py count
|
||||
|
||||
State is kept in tasks.json next to this file. The same minimal app from Module 1 onward; the
|
||||
target your "add a command" skill extends.
|
||||
@@ -32,7 +32,7 @@ def save(tlist: TaskList) -> None:
|
||||
def main(argv: list[str]) -> int:
|
||||
tlist = load()
|
||||
if not argv:
|
||||
print("usage: python cli.py [add <title> | list | done <index> | count]")
|
||||
print("usage: python3 cli.py [add <title> | list | done <index> | count]")
|
||||
return 1
|
||||
|
||||
command = argv[0]
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
"""Test suite for the tasks-app. Run from this folder with:
|
||||
|
||||
python -m unittest
|
||||
python3 -m unittest
|
||||
|
||||
Your "add a command" skill should ADD a test here for every new command. The point is to assert
|
||||
intended behavior, not just that nothing crashed.
|
||||
|
||||
Reference in New Issue
Block a user