Thanks! I did put a lot of thought into planning it, so that it covers all the topics with little wasted effort. I really want to respect my viewer's time - so I really appreciate your comment :)

I agree!! this video is best pytest tutorial

Agree 💯

Thank you! Glad you enjoyed it :)

Thanks! I appreciate that.

Thanks! That's my goal with these videos :)

Glad you liked it :)

Thank you for the thoughtful comment :) Glad you found the content useful. Stay tuned, I hope to provide more useful content right here on this channel.

Thanks! I hope it helped!

@@pixegami There is only one thing missing from this video and pretty much everywhere I've looked on the Internet: How to import a function in a directory from a file in another directory at the same depth. This is import for testing packages with the directory structure /src/file with /test/test_file or when one package is accessing another one. A video on that would be terrific!

Really glad to hear that! Thank you :)

Thanks! I know everyone is busy and want to learn as quickly as possible, so I aim to keep the content lean. Good to know that the effort is not wasted :)

Awesome, thank you!

Testing seems hard because I think there's not enough education about it! But I'm glad this video helped!

Thank you for your kind comments :) I try hard to structure the content to be as direct and useful as possible, so I appreciate hearing whenever it helps someone out.

Thank you, I appreciate your comment!

Glad you enjoyed it!

Glad you liked it!

Thanks! I'm glad you think so :)

Thanks! I appreciate the support :)

Thanks! I appreciate the comment.

Glad it was helpful!

Thanks! More to come. Feel free to suggest topics you'd like to see.

That's a great idea - thanks for the feedback :) I can definitely cover more testing topics.

Yes, please!🙏

Thanks! Hope it was useful.

Thank you!

You're very welcome!

Glad it was helpful!

Thank you! Corey Schafer is a legend and I'm humbled to be compared to them.

Thank you! Glad you found it clear!

Thank you! Glad it was helpful!

Thanks!

Thank you! 😃

Glad you liked it!

You're welcome!

Interesting - I hadn't considered a part 2, but I'm keen to hear your use cases for the things you mentioned (particularly about AI testing - do you have a use case in mind for that)?

@@pixegami I worked on a personal project where a pokerbot would receive real images of pokercards and then used a simple CNN to decide which card it was. In order to test the flow I had to import the model, retrieve some test images etc. But I also just wondering in general how to combine unit testing and data science. I really enjoy developing well tested code and these jupyter notebooks are a nightmare to work with when I do anything AI related

Awesome! Glad to hear that!

Thanks! I appreciate the comment :)

Glad it was helpful!

Glad you liked it!

You're welcome! Good luck.

Glad you like it!

Glad it helped!

Great questions! 1. How do I return a list of values or (anything else) from a fixture? Well, a fixture can return any type of value. So you could have a fixture that returns a tuple. Or you might choose to have a Class or a module that groups together a bunch of different values you want to use together. You are also not limited to using one fixture per test. If you made another fixture called "cart2", then you should be able to use both fixtures in the test by writing: `def test_can_get_total_price(cart, cart2)`. Take a look here for more examples: docs.pytest.org/en/6.2.x/fixture.html 2. You don't see anything being passed in to `mock_get_item` because we never use it directly in the test. We *assign* it to our item_database's "get()" function: "item_database.get = Mock(side_effect=mock_get_item)". Then we call `cart.get_total_price(...)`, which then goes on to call the item_database.get() with our arguments: "total_price += price_map.get(item)": github.com/pixegami/simple-pytest-tutorial/blob/aa65d4b457039dddaeb0a75a359f223a25ec3d09/shopping_cart.py#L23 So when you say " item_database should still be an empty class since the .get method does nothing" - it's actually not true because we *mocked* the get() method to do something for us with this line. We basically 'replaced' the functionality of `item_database.get()`: github.com/pixegami/simple-pytest-tutorial/blob/aa65d4b457039dddaeb0a75a359f223a25ec3d09/test_shopping_cart.py#L42 Hope this helps!

Thank you!

Glad to hear it!

Glad it was helpful!

Glad it was helpful!

Glad it was helpful!

Glad it was helpful!

Glad you liked it!

Thank you, I appreciate your comment!

Thanks for the feedback! Glad you enjoyed the video. And yes, I agree the keyboard is too loud. Sorry! I've actually upgraded my Mic to a vocal mic, and I'm using a different (softer) keyboard now in my newer videos so I hope it'll feel/sound better for you.

I hope it was helpful!

Glad it was helpful!

Thanks for the encouragement!

Glad it helped

Ah, thanks for calling out!

Thanks. I appreciate it!

You're welcome!

Awesome, thank you!

Thanks!

Thank you! I use monokai.pro/ - I've tried a lot of different themes, but I always come back to this one.

Glad it was helpful!

Thanks and welcome!

Thank you! In this video I'm using Ubuntu Linux. It's probably my favourite programming environment, although these days I'm using a Mac because I find I also need a lot of creative software (to make the actual videos).

Not yet, but I'll note it down as an idea that my audience wants! Thank you.

Hmm, not sure where that is coming from. I'd probably recommend just tracing back the error to find where it's coming from, and also just updating all the dependencies so they are all on the latest version. But if it's just a warning, I don't think it should impact you.

Glad it was helpful!

Here's a section in the doc on how to specify which tests to run: docs.pytest.org/en/latest/how-to/usage.html#specifying-which-tests-to-run E.g. for a specific function you can run `pytest tests/test_mod.py::test_func`.

Yup! In unit tests, we don't want to use real databases or values, so we "mocK' them. We're saying "pretend I have a database, and when I query for 'x', give me '5'." This way we can just test that specific unit of the code (usually just a class or a function) without having to worry about the other parts of app.

In this video I just used a DURAGOD keyboard with blue-key switches. I've since changed now to a Moonlander keyboard with brown switches. They keyboards don't really make too much difference to me as long as they are the thicker mechanical types.

I have a video and a GitHub repo covering the Ubuntu ZSH theme I use: github.com/pixegami/terminal-profile

When you first write the test, they should fail because in "test driven development" you write tests before the feature. And so you then develop the feature, and if the feature works properly, the test should pass (that's how you know the feature works). In a team environment, you could have different people writing tests and writing features - allowing you to run tasks in parallel. Once the tests are passing, you basically just run the whole suite every time more features get added to the project. It's very common for new features to break something that was developed 6 months ago, for example. So the tests will help detect when that happens, and you can fix it.

Thanks for the feedback. I've reduced the ad settings so now it should be a smoother viewing experience.

When you ask "how mock_get_item knows that there are two items" --- what indicates to you that it knows anything beyond what we told it to expect in the code snippet? `mock_get_item` actually doesn't know that there are two items (in the cart). All it knows is that when we call it with "apple", it should return 1.0, and when called with "orange" it should return 2.0. The *cart* itself knows that there are two items in the cart (because we added it), but the cart's database has been mocked with mock_get_item, so no real database is involved. Code for reference: github.com/pixegami/simple-pytest-tutorial/blob/aa65d4b457039dddaeb0a75a359f223a25ec3d09/test_shopping_cart.py#L36-L40

Sorry I haven't done any Django projects yet but it's on my list!

Cool@@pixegami

Python is a great programming language to learn! I have a complete playlist on a learning roadmap and how to install it and learn all the basics here: kzfaq.info/sun/PLZJBfja3V3Rsbiz84Z63IXnTQZH_Rnfuo&si=-hMurnRNSf2s7J_m

Great suggestion! `mock.patch` works too, and is probably a good way to do it. I didn't choose to use it here mainly because I wanted to make the relationship between the mock and the dependency clearer. Introducing mock.patch would introduce some new mental concepts (with it being a decorator), and I didn't want that at this stage in the tutorial. Now, in actual real projects I've used mock.patch before, but it started to become annoying when there's maybe 5-6 things I needed to patch for one test. A lot of nesting, ordinal arguments, and a lot of repetition across various test cases. I am now learning towards fixtures instead, to set up more complex mock behavior.

For Ubuntu, I use the default terminal but I customize it with Oh My ZSH and some colors. Here's a quick video and repo on that: kzfaq.info/get/bejne/i9yJaMR3rbTTdas.html

I hope it's useful!