Migrate to pytest about ihatemoney

[Glandos]

unittest.MagicMock and patch

Not yet identified

flask_testing.TestCase

• Could be replaced by a fixture to create the app, as before.
• Creating the database seems to be left as an exercise for the user.

unittest assertions

Not yet identified

[hamma741]

It's great that you are considering moving away from Flask-Testing and exploring other options for writing tests in Flask. As you mentioned, using fixtures with pytest is a popular approach for testing Flask applications.

In addition to pytest, there are other testing frameworks that you may want to consider, such as nose or unittest2. However, pytest is widely used and offers many features that make it a popular choice among developers.

To get started with using pytest for testing Flask, you can take a look at the official Flask documentation on testing with pytest (https://flask.palletsprojects.com/en/2.1.x/testing/pytest/). This guide provides an overview of how to use pytest with Flask, including how to create test fixtures, how to write tests using the Flask test client, and how to run tests using pytest.

In general, moving to pytest involves refactoring your existing tests to use pytest fixtures and syntax. This may take some time, but it can provide significant benefits in terms of test organization, readability, and maintainability.

Some benefits of using pytest over Flask-Testing include:

Pytest offers a more powerful and flexible testing framework, with many built-in features for test discovery, test organization, and test execution.
Pytest has a large and active community, with many plugins and extensions available for customizing and extending its functionality.
Pytest is compatible with many other testing tools and frameworks, making it easy to integrate with your existing development workflow.
Overall, moving to pytest can be a great way to improve your testing process and ensure that your Flask applications are robust, reliable, and easy to maintain.