Feature/refactor tests plugins

[guscardvs]

Hi, here are some proposed changes to the project. Changes:

• Splitted files in a package folder
• Added custom exceptions without breaking tests
• Added static typing for main file
• Created pytest plugin
• Dropped tests from unittest in favor of pytest
• Added pytest-asyncio as dev dependency to facilitate tests
• Created context manager and decorates to reduce code boilerplate
• Bumped requirements to more uptodate versions
• Dropped support to python version <3.8 Closes #12

[felliott]

Hey @guscardvs!

Thanks for submitting this. This looks like the direction we want to move for aiohttpretty and a quick skim seems okay, but I'll need to spend some time carefully reviewing it. The apps we maintain that use this are still stuck on Python v3.6+, so I'll need to do some testing before we can adopt it.

In the meantime, I have a few questions:

• Do you have or know of projects that are currently using aiohttpretty? I'd be interested in knowing what new functionality is being used. I'd also like to know what other apps/libraries to test before releasing a new version.
• Related to the previous question: did you do this by hand or use a tool to refactor it? Either way is fine, but I noticed some comments were lost in the process. I'd like some context on whether that was intentional or accidental.
• Not a blocker, but why did you switch to poetry? I don't know much about current best practices, I'm just curious.
• What is .cz.toml? I'm not familiar with that tool.

I also have some code nitpicks:

• Some of your commits have added ^Ms to the end of the lines. Could you remove those?
• Our develop version (pinned, but never released to pypi) was set to 19.0.0. Instead of bumping to 1.0.0, could you bump to 22.0.0? Our org has moved to CalVer for versioning releases.
• The o was removed from the maintainer email here

Thank you, and have a great day! @felliott

[guscardvs]

Hi @felliott,

Let's one question at a time, 😄.

• Most of my projects use aiohttpretty, since I'm a big fan of aiohttp and prefer to abstain from mock.patch. The features I missed mostly, which lead me here, were pytest plugin, a simple context manager and decorator, instead of the manual activate/deactivate
• I mostly refactored by hand, but used Sourcery to help with some minor stuff, such as prefer comprehensions over for loops. Most comments were accidental, no problem placing them back. 😄
• I switched to poetry mostly because it's more performant than pdm and Pipenv as a package manager and it has builtin build and publish features, which reduces the need for twine or any other package management or pypi build/upload tool.
• .cz.toml is the config file for Commitizen

About the code nitpicks, i will have them solved right now :).

Best regards, @guscardvs