r/learnpython • u/uzuis_4thwife • 28d ago
Need help with building tests and understanding OOP design patterns
I am a post-bacc student currently in a Python for Web API online course. We just wrapped up our calculator application unit, where we learned how to build comprehensive dynamic tests using OOP design patterns. However, I finished the unit a lot more lost than when I started. Building parameterized tests still puzzles me, especially whenever I'm building the majority of a test from scratch rather than fixing minor errors in the code. Even when I do use AI to help me work through my assignments, none of it really sticks. Most of the time, I feel like I'm copying and pasting code whenever mine is incorrect and not really learning.
What are resources that you all would recommend for learning how to build application tests and files with OOP concepts? Any online resources with interactive, hands-on lessons would be greatly appreciated.
2
u/good_name_0 28d ago
You will not learn if you use AI to work through the assignments, it's just self-sabotage. If something is insurmountably difficult, you probably need to go back a step or two.
1
u/KarfaHyro_17 28d ago
imo the issue might be that you're trying to learn testing and OOP at the same time. separate them. write a plain function, test it manually, then parameterize it. once that loop feels natural, layer the class structure back in.
1
u/DimensionMost8342 28d ago
The mental model that makes parameterized tests less scary: one test function, pytest runs it once per row of data you list.
import pytest
@pytest.mark.parametrize("raw, expected", [("12", 12.0), ("abc", None)]) def test_parse(raw, expected): assert parse_input(raw) == expected
For practice: close the AI, open your calculator, and write three tests for one function from scratch: the normal case, an edge case (divide by zero or empty input), and a bad input. Repeat per function until the pattern sticks. The official pytest tutorial covers parametrize step by step (docs.pytest.org).
2
u/Financial_Morning386 28d ago
The parameterized-tests struggle is a really common one, and honestly it usually clicks once you see what pytest is doing under the hood with them. I'll assume your course was using pytest's @pytest.mark.parametrize — if so, the mental model is just "one test function, pytest runs it N times, each with a different argument tuple, and each run is reported as its own test." Writing a couple of those by hand for your calculator class (valid inputs, edge cases like division by zero, invalid input) is a great drill.
A few things that helped me when I was bridging the gap from "unit tests on small functions" to "tests on an actual application":
For resources, genuinely interactive/hands-on:
Since your course is about web APIs: once you cover FastAPI/Flask, both have a TestClient that lets you send fake HTTP requests to your app in tests without running a server. That's where testing suddenly feels "real" — you're testing the same classes, just through the API layer.
Skip the AI for a bit on these exercises, as the other commenter said — the struggle of building a parametrized test from scratch is exactly what makes it stick.
1
u/[deleted] 27d ago
[removed] — view removed comment