Metadata-Version: 2.4
Name: pytest-easy
Version: 0.0.2
Summary: Pytest, but made easy
License-File: LICENSE
Author: danialcala94
Author-email: danielalcalavalera@gmail.com
Requires-Python: >=3.8,<3.14
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Requires-Dist: printer-easy (>=0.0.2,<1.0.0)
Requires-Dist: psutil (>=7.2.2,<9999.0.0)
Requires-Dist: python-dotenv (>=1.0.1,<9999.0.0)
Project-URL: Homepage, https://github.com/Implosiv3/pytest-easy
Project-URL: Issues, https://github.com/Implosiv3/pytest-easy/issues
Description-Content-Type: text/markdown

# Pytest, but made easy

The easiest way to test your projects with `pytest`.

# Functionality
Simplify the way we do our tests in python, and also is able to run the tests individually to be more accurate but a bit slower.

I had some tests that, when running all together, were failing due to memory issues. This is the way I solved it, and also I can log the results of my tests and clean the tests files folders very easy each time the tests are executed.

# Usage
The `tests` folder will be your new friend. Keep a `test_general.py` to always do a simple test. Have the `conftest.py` to configure what has to be done before and after the tests are running.

This will execute the tests and remove all the new files in the `test_files` folder that were not before the tests were executed, or you can simply comment the `test_files_handler.delete_new_files()` line before running them, so the generated files are not removed in that execution, uncomment it, and they won't be removed in the next execution because they were already there.

That is the easiest way to test and see the file results.

Check `test_various.py` to see more examples.
