getting started with pytest (beginner - intermediate) anthony explains
HTML-код
- Опубликовано: 22 янв 2023
- I realize I've talked a lot about pytest on the channel, but never given it a proper introduction!
- testing a cli with pytest: • python cli tested with...
- parametrize: • pytest's parametrize (...
- testing lru cache: • testing functools.lru_...
- why pytest.mark.usefixtures? • why pytest.mark.usefix...
- parametrize permutation: • pytest: parametrize pe...
- testing exceptions: • pytest: testing except...
- testing output: • testing output with py...
- all pytest statuses: • pytest: xfail vs xpass...
- testing environment variables: • pytest: testing env va...
- conditional contexts and pytest: • what is nullcontext? (...
- pytest: all about fixtures: • pytest: everything you...
playlist: • anthony explains
==========
twitch: / anthonywritescode
dicsord: / discord
twitter: / codewithanthony
github: github.com/asottile
stream github: github.com/anthonywritescode
I won't ask for subscriptions / likes / comments in videos but it really helps the channel. If you have any suggestions or things you'd like to see please comment below! 
Наука
8:20 pytest also prints out whatever was written to stdout whenever a test fails. So if you're debugging a failing test you can read the output even without using -s.
-v{1,3} is also very helpful when tests with a more complex comparison fail, e.g. long strings, lists/tuples/dicts with many items. It shows you exactly where the difference occurred, what item is missing etc.
It helps me a lot breaking this down
Thanks a lot for the video. Coming from other language backgrounds, it helped a lot to clarify some info. Plus, it was short and enlightening
Awesome video! can we also have a video on Mock, patching, monkey patch..etc please!
One of the top python packages! 🙂
Truly one of the python packages of all time
Didn't know that including __init__.py would resolve name collisions - thanks!
Nice video, just checked I was sure unit test wasn’t in Python 1. Python predates junit by about 7 years and unit test was inspired by junit. python
20 February 1991. JUnit was born on a flight from Zurich to the 1997 OOPSLA in Atlanta.
great video
Thanks!
Thanks for the video! Many of your repos have testing directory, what do you store there? A code that is related for tests but you keep it separate because tests directory should contain only tests? Or my guess is wrong
if you search my channel I did a video on my project structure
please explain the plugins for pytest!! great video!! thumbsed upppp!!!
Thanks, Anthony. Can you make a video about 'indirect' in parametrize?
And also request param in fixtures?
personally I don't think anyone should use indirect
Thanks for the video!
It would be helpful to get a more advanced follow up video about fixtures, patches and so on :)
check out the description :P
I assume the `-s` and suppression of I/O extends to the code not only in the test file (t_test.py) but also the original file (t.py)?
yep yep, i/o is controlled globally
great video, do u have any idea on best way to configure test data for different environments (dev, staging etc) in pytest?
I would hope you're not running pytest in staging?
@@anthonywritescode It is running in staging but its blackbox level test script, but i was just curious how would one manage test data in this situation.
TIL about -s for print debugging an incorrectly passing test. I've normally just gone with the tried and true 1 / 0 in the test if it comes to that. haha
The plugins certainly make the tool shine brighter than it already does. Off the top of my head, pytest-randomly and pytest-repeat are two I use regularly to shake out and expose tricky pollution.
And I have been using the infinitely more verbose --capture=tee-sys :-!
flask app is dockerized. Uses rq worker, redis, postgres as compose services. How should one thing about testing such application?
you mock the output from those services to test your logic
Great video!
I've quickly tested some time ago unittest from python and I found out that writing assertion keyword is not strictly prohibited, maaaaybeee they changed something? I don't know. But pytest is by far most useful 3rd party tool downloadable from PIP! Thanks for sharing this tutorial!
there's nothing stopping you from using plain assert, but your error messages will be useless
@@anthonywritescode Oh, okay then. thanks! :)
i did learn OOP way in Python just to understood pretty well unittest code examples.
Now i just accidentally here Pytest and saw your video, while i did research on youtube how it looks like.
And i like that pytest , it does not strictly used Class Based written test.
I also enjoyed my learning on unittest framwork using Class Base.
But i do believe in unittest you can do it in by writing functions instead like the Pytest. But not really good idea since the documentation does not mention something like that, i could also be wrong since i am still fairly new to writing unit test code, when i did my first python project, all i did was like intuition. No written test and it was horrible experience because it was hard to identify the bugs on the project.
But yeah lesson learned and i better write a test whenever i write a functionality of the program.
Your video showing pytest was pretty great, i have no idea how great is pytest in general. looks more simpler in terms of usage compare to unittest in my opinion.
I have still to open my OOP book in Python, just to make myself not getting lost in the middle.
Thanks for creating the video of demonstrating pytest.
Just notice you type in terminal: " babi .py "
what is that "babi"?
It looks like nano text editor, i guess it is? you just make some alias for nano text editor?
I made my own text editor :D
I never knew there was a name to call how you name your variables:
camelCase
snake_case
PascalCase
kebab-case
# just in case
whats with the keyboard view?
Hey Anthony! Why do you not like oop? 😊 its a battle am fighting to learn or not but i checked many of your repos and didnt see you using classes, so was hoping to hear your thoughts
it's terrible for large code cases and tends to encourage poor patterns. when a lot of people say "I'm doing oop" I find most of them are instead doing "I'm too lazy to import what I need so I'm using inheritance for convenience"
@@anthonywritescode thank you for responding and everything you share through this channel.
I honestly prefer unittest. It is just nice to have it integrated in the language. Other than that I don't use it very differently from how you use pytest in this video.
why do you put an underscore infront of main like _main.py, and the other files
it is an attempt to tell people to not muck with the internals
Why all files of pyupgrade starts with _?
it's a commandline tool -- there is no intended python api -- but people still reach into the internals and muck with them nonetheless
Great video. Thank you for it!
One thing that I was wondering about is that, as you mentioned in the video, for basically every python file, you create a corresponding test file. Personally, this makes a lot of sense to me and keeps everything in order, but previously in a clean code video, I thought they stated that this could result in overcoupling.
Part of the video: ruclips.net/video/58jGpV2Cg50/видео.html
Are they talking about something fundamentally different, or how would you explain this?
"clean code" is a lie -- and you should be immediately skeptical of anyone trying to sell you that lie
@@anthonywritescode Could you maybe detail this a little more?
@@anthonywritescode dirty code is more fun anyway
😁
I've heard about this great tool, pre-commit. It's from this really cool guy, you should definitely give it a try *wink*.
It would be nice to have a "getting started with pre-commit".
yeah I've recorded this and thrown it away few times -- maybe the next recording I'll be happy with