Added github actions to run uiTests

[epicadk]

Description

Include a summary of the change and relevant motivation/context. List any dependencies that are required for this change.

Fixes #168

Type of Change:

Delete irrelevant options.

• Quality Assurance

Code/Quality Assurance Only

• New feature (non-breaking change which adds functionality pre-approved by mentors)

How Has This Been Tested?

Describe the tests you ran to verify your changes. Provide instructions or GIFs so we can reproduce. List any relevant details for your test.

Checklist:

Delete irrelevant options.

• My PR follows the style guidelines of this project
• I have performed a self-review of my own code or materials
• I have commented my code or provided relevant documentation, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• Any dependent changes have been merged
• I have written Kotlin Docs whenever is applicable

Code/Quality Assurance Only

• My changes generate no new warnings
• My PR currently breaks something (fix or feature that would cause existing functionality to not work as expected)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been published in downstream modules

[epicadk]

@isabelcosta done can you review ? The tests are failing because the existing tests fail.

[isabelcosta]

@epicadk is it possible to have this as a separate check on GitHub checks 🤔 to separate build from tests so we know right aways why something is failing. Would you know how to do that?

[epicadk]

@epicadk is it possible to have this as a separate check on GitHub checks 🤔 to separate build from tests so we know right aways why something is failing. Would you know how to do that?

Hmm it is but we can also check the details to view which test has failed , and it would also avoid setting up of another Ubuntu system.

Let me know how I should proceed.

[epicadk]

@epicadk is it possible to have this as a separate check on GitHub checks 🤔 to separate build from tests so we know right aways why something is failing. Would you know how to do that?

Hmm it is but we can also check the details to view which test has failed , and it would also avoid setting up of another Ubuntu system.

Let me know how I should proceed.

@isabelcosta I created a separate workflow using mac-os ( as that is what was recommended in the docs here) I think it is working as expected now please review.

[isabelcosta]

I am not very aware of how tests are run in Android, but this looks good to me. I saw the additional PR check and I think that looks good separate from the build workflow. I will ask for more reviews on this from the community.

Thank you so much for working on this @epicadk 🙌

[annabauza]

Suggested minor changes to observe pas and pushes to master branch as well.

[annabauza]

Prs not pas

[annabauza]

As in comments

[epicadk]

I've made the requested changes @isabelcosta @annabauza. : )

[annabauza]

💯

[epicadk]

I just removed the comments in the yml file. Should I squash the commits?

[isabelcosta]

I just removed the comments in the yml file. Should I squash the commits?

No worries. No need for that, I will squash anyways when merging @epicadk :) thank you so much for working on this one 🙌

[annabauza]

💯

[isabelcosta]

@epicadk could you please update this branch, not sure if the tests are already fixed 🤔 and if they are not yet fixed, we have to pin community again to help us fix the tests

[epicadk]

@epicadk could you please update this branch, not sure if the tests are already fixed 🤔 and if they are not yet fixed, we have to pin community again to help us fix the tests

Ran the tests locally and they haven't been fixed yet. I'll look into this.

Also I had brought this up in a session but sometimes the sessions times out and that is why the tests fail.