Create functional testing files and ci process

[andrewtavis]

Terms

• I have searched open and closed issues
• I agree to follow Scribe-iOS' Code of Conduct

Issue

Testing for Scribe and a continuous integration process would be very helpful to assure that pull requests can merged without issue. Discussions of best practices as well as how best to integrate the process into pull requests would be a first step in this issue. This would be followed by writing tests for a baseline, and then adding a ci.yml file to a workflows directory in Scribe-iOS/.github.

[andrewtavis]

The issues with Scribe not functioning as on Simulator means that testing should be a priority, potentially even for the next release. Specifically #96 seems difficult to test for on Simulator. One option going forward would be to integrate a device testing service like Browserstack, which is available free for open source. There's also the ability to add GitHub Actions integration, which then could function as a part of the general CI process.

[SaurabhJamadagni]

Currently reviewing the following documentation @andrewtavis.
Docs:

• Apple's XCTest docs

Articles:

• Unit testing in Swift: Fundamentals
• Getting started with Unit Tests in Swift

Will have a brief summarisation by EOD. Also, checking out Browserstack. Thank you for creating all the issues 😄 🚀