ISSUE-10 - Allow host machine to run tests

[AdonisCodes]

Reason

Currently one must run all the tests via docker-compose in order to see if their changes don't affect the current suite of tests. The majority of the time a dev only wants to run a single test, or a small subset of tests to see if their changes affected what they want. This speeds up development.

This PR closes #10

Tech Details List

• edits docker-compose to use host network
• edits base tests to also use localhost:4444
• edits documentation to showcase dev env usage

ISSUE-10

Testing

Steps:

1. Run required commands to test all the modified code.

docker compose up selenium httpd -d
swift test

Output:

• Ensure tests run on your host machine

Testing QA

Test this in Xcode / Vscode to see if a singular test run passes by running a single suite / test

Review Checklist

• Properly Typed All Symbols
• Updated All documentation that the code touched
• Testing Fresh Deployment works with a singular command
• Tests cover all discovered edge cases
• Handles all errors gracefully, ensuring unexpected errors are tracked & monitored
• Code Structure Correctness
• Cleanup of temporary/noise/testing files
• Load Testing: Ensure the code handles expected traffic efficiently

[vimscientist69]

@AdonisCodes, do you think it would be a good idea to have a reviewer checklist on each PR template? This way, we can ensure that all PRs are reviewed properly. If so, can you create an issue on the .github repository for that? Thanks.

[vimscientist69]

It looks good overall. Feel free to merge once replying to the one comment I left earlier. Good job.

[AdonisCodes]

@AdonisCodes, do you think it would be a good idea to have a reviewer checklist on each PR template? This way, we can ensure that all PRs are reviewed properly. If so, can you create an issue on the .github repository for that? Thanks.

Yes. We can have the PR template be updated to include Asignee Checklist and Reviewer Checklist sections int he template.