Pytest is the most widely used Python testing framework, so I recommend looking into that. More on reddit.com

Hey guys, I´m actually doing my first larger project with python and this brings testing with it. So I never really tested a… More on reddit.com

pytest is pretty much the de facto standard in the industry, and it's compatible with unittest tests if you want/have to use both. To go even more meta, tox is used to run pytest on multiple versions and platforms. You can't go wrong with either, but pytest generally results in cleaner and more reusable test code. Its fixtures are amazing for reusability. More on reddit.com

I use PyCharm and not sure if I should be using the built in "New Unit Test" feature which uses the unittest module, or if I should just be writing from scratch... I would learn how the framework works without involving the IDE. Once you understand it, then you can use the IDE to make things simpler if you want. I've seen too many beginners use these kinds of shortcuts and end up in a bind because they don't actually understand what they are doing, just how to make some random IDE do it for them. With this kind of thing, I learn best by example. Although general guidelines would be really helpful and appreciated, it'll be even better to just see someone's unit tests that have been deemed "good" by someone other than myself. If anyone could help me out I'd really appreciate it Thank you :) I believe ArjanCodes on YouTube has a video on unit testing. I do know that he has a few series where he "fixes" someone else's code and that includes unit tests. My hints: Tests are just Python Unit tests aren't special. Most of what a testing framework does is run the tests. They provide a lot of other convenience code as well, sure, but from a beginner standpoint, a unit test is just a normal Python function that checks some other piece of code. So if, for example, you had a function: def add_two(n: int) -> int: return n + 2 then you would want a few unit tests to make sure it's working correctly: from module import add_two def test_add_two_positive(): assert add_two(5) == 7 def test_add_two_negative(): assert add_two(-7) == -5 Generally, a test does three things: import some code to test, run a single use-case, and check that the output is as expected. This means that additional use-cases should probably be separate tests. While a little more effort to write (by hand, your IDE should help with this eventually) doing so makes discovering your bugs much easier if the test__with_an_empty_list test fails instead of the test_. Tests should be written first Ideally, you know what your function is supposed to do before you write it, so write your tests first, then when they all pass you know you're done with the function. This is known as "Test-Driven Development" or "Red, Green, Refactor". Tests should test all possible inputs AND all possible failure cases One of the benefits of tests is not only do they tell you when your code works, but they tell you when it stops working. So test for edge and failure cases. Consider PyTest pytest is a backward-compatible replacement for unittest and works with normal assert statements. It also has a bunch of additional features for advanced testing. Everything starts with test Because the primary purpose of a test framework is to run tests, it needs a way to find them. You can customize this, but the easiest way is to just make sure everything test-related starts with the word "test". Put your tests in a "tests" folder. Write your tests in files named "test_.py", name your test classes (if you have them) TestSomething and name your test functions test_something_something. More on reddit.com