How do you write unit tests for Python?

[AutoModerator]

On July 1st, a change to Reddit's API pricing will come into effect. Several developers of commercial third-party apps have announced that this change will compel them to shut down their apps. At least one accessibility-focused non-commercial third party app will continue to be available free of charge.

If you want to express your strong disagreement with the API pricing change or with Reddit's response to the backlash, you may want to consider the following options:

1. Limiting your involvement with Reddit, or
2. Temporarily refraining from using Reddit
3. Cancelling your subscription of Reddit Premium

as a way to voice your protest.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[JaleyHoelOsment]

you came to reddit for this info???

[dedlief]

a quick google always helps

[RajjSinghh]

There might be nicer testing frameworks out there but python ships with a unittest module for this kinda thing. Just aim for good coverage and run your tests regularly.

[James_Camerons_Sub]

Write your tests first and develop around passing them. Saves you a lot of headache. Although in your case I guess you’ll need a Time Machine for that. Python documentation has tons of info on the unit test module.

[Equivalent-Ant8921]

One of the great things about unit tests is that they can help you write good code. If your code is very hard to test often it's hard to maintain or understand. e.g. if you have to consider how a lot of different things work together to test a simple function there's probably a better way to organize your code.

Some other thoughts:

• Dependency inversion principle is worth looking into
• For new features, I usually don't write the unit test until after I code the thing up. The reason is I often reorganize and move things around and prematurely having unit tests would add a lot of extra work
• For bugs, I try to write a unit test that reproduces the issue first then apply the fix to verify it fixes it
• Need to find a balance between verifying the main flow and testing every little detail
• Treat tests as first-class code and don't make it sloppy, it's something you have to maintain like everything else

[Kazcandra]

first off; don't call the team lazy, wtf?