Refactor and fix tests

[shubham599]

Contributes to #46

What did you do?

Refactored tests:
Now all of the tests are under the 'testing' directory. They are further categorized into 'unit' and 'integration' tests.

Removed duplicate test:
'test_post_headers.py' was actually doing a subset of what 'test_mark.py' was doing - so I've deleted 'test_post_headers.py'

Fixed imports:
I've added 'init.py' files to the project directory, as well as the test directories. This allowed me to import stuff 'the python way' (or rather, 'the fastapi way'), removing the need to add filepaths to the system path variable for imports.

Why did you do it?

Appending filepaths to system path variables is not the ideal way to handle imports. Further, organizing all tests under a single directory helps keep imports clean, and can also be beneficial in CI/CD (we can just call 'pytest' in the GitHub Action that compiles the code, and it will run all the tests itself).

How have you tested it?

Ran pytest on the project directory - all tests are running and succeeding

Were docs updated if needed?

• No
• Yes
• N/A

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new console logs
• Fixes entire issue
• Partial fix for issue

[github-actions]

👋 Hi! This pull request has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed in 14 days.