← कोर्सच्या मुख्य पानाकडे परत

🗓️ अभ्यास योजना — 12 धडे, 4 आठवडे

~3 sessions a week: read the lesson (~15 min) + run and change its section of exam/demo.py (~25 min). Tick lessons off — progress is saved in this browser.

🐢 स्थिर: आठवड्याला 3 सत्रे → 4 आठवड्यांत पूर्ण.
🐇 वेगवान: प्रत्येक भागासाठी एक weekend → 3 weekends मध्ये पूर्ण.
💰 खर्च: शून्य. तुमच्या लॅपटॉपवर Python 3.
0 / 12

WEEK 1 💸 Questions and the right questions

Why test, unit tests, test design. Lab: grade papers out of 200 and 300; write a failing and an erroring test; build the boundary table for every grade line.

~35 मि.
~35 मि.
~40 मि.
🏁 Checkpoint: you can find the bug at 34.5 with boundary values and say what a passing test does not prove.

WEEK 2 🗂️ Answer sheets and stand-ins

Fixtures, test doubles, integration. Lab: add a builder method; run shared-fixture tests in both orders; stub a 404; make the fake store and SQLite disagree.

~35 मि.
~40 मि.
~35 मि.
🏁 Checkpoint: you can choose between a stub, a fake and a real database for a given test — and say what each can miss.

WEEK 3 🤝 Promises, pyramids, properties

Contract tests, e2e and the pyramid, property-based testing. Lab: break the contract three ways; change the e2e count in the cost model; try new seeds and a new property.

~40 मि.
~35 मि.
~40 मि.
🏁 Checkpoint: you can explain why a rename breaks a contract, why e2e tests stay few, and how shrinking reaches 34.5.

WEEK 4 🧬 Mutants, clocks, CI

Coverage and mutation, flaky tests, CI and TDD. Lab: add a question that kills a survivor; replay the 23:30 failure; TDD a new rule red → green → refactor.

~40 मि.
~40 मि.
~40 मि.
🏁 Checkpoint: 🏆 Capstone: write the test plan for the school's fee calculator: the boundary table, the doubles and the contract for the payments service, one property, a mutation target, the flaky-test rules, and the CI order.

🎓 12 / 12 — every paper marked!

Next: the CI/CD school runs these tests in real pipelines, the API school designs the contracts, and the School portal has the rest.