Split the tests directory into unit and regression

[surbhigoel77]

Description

Restructured the tests directory and split it into unit and regression modules. The segregation would facilitate a structured execution of the tests and would also provide easier navigation. Also added a README.md to empty folders to make them trackable by git.

Fixes #143

Type of change

• [ ] New feature (non-breaking change which adds functionality)
• [x] Optimization (back-end change that speeds up the code)
• [ ] Bug fix (non-breaking change which fixes an issue)

Key checklist

• [x] Make sure you've run the pre-commit checks: $ pre-commit run -a
• [x] All tests pass: $ poetry run pytest

Further checks

• [ ] Code is commented, particularly in hard-to-understand areas
• [ ] Tests added that prove fix is effective or that feature works

[surbhigoel77]

This looks generally good for me. I am just wondering whether we want to use these as packages, in which case we need a init.py ( see https://docs.python.org/3/tutorial/modules.html , section 6.4). If we don't need it at the moment or in the foreseeable future it's fine as it is.

I will add init.py to the unit/regression subfolders to allow us the flexibility of using them as packages in future.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ee9eb7f) 94.09% compared to head (1091eac) 94.09%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## develop #151 +/- ## ======================================== Coverage 94.09% 94.09% ======================================== Files 21 21 Lines 1134 1134 ======================================== Hits 1067 1067 Misses 67 67 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[davidorme]

Looks good to me too.