[Feature] Test project on CI

[blyscuit]

Why

CICD scripts are included in the project but it is unused.

Acceptance Criteria

• CI should run test for the project when pushing a new commit.
• Generate testing report to the pull request.
• Integrate SonarCloud or provide screenshot of testing reports created via CI.
• If ay step is not possible, explain why.

[lngyeen]

Hi @blyscuit Forgive me, to be honest it's been a long time since I worked with CI/CD related tasks. Please allow me not to make this request. However I can show you the CI process in the current project I'm working on (i designed and wrote this process but long time ago), it looks like this:

Basically the process is the same as on other CI services. The branches that need to be triggered will be main, develop and release/. On Azure pipeline there is a little difference in running tests when there is a pull request. We can place a build validation in any branch (usually develop), a pull request can only be merged if this build validation is successful (usually we will put build and test stages in this build validation ). Other branches depend on our purposes, but usually when there is a commit to `release/branch, we will build and upload to TestFlight/FireBase/AppCenter, and when there is a commit tomain` branch, we will build and upload it to TestFlight/FireBase/AppCenter. upload to AppStore. In the Azure pipeline, I almost don't have to use Fastlane because the tasks (actions) related to building and deploying iOS apps are all supported (or just need to install a few very popular Plugins).

[blyscuit]

@lngyeen It seems that you have everything needed to run CI, if you could provide a screenshot of the running CI would be enough to clarify this issue. But no need to focus on this if it will take a long time.

[lngyeen]

@blyscuit Sorry i did not have enough time to try these stubs. I was focus on other issues ;)