Add a new page with guidance on how to write UI/e2e tests for a Teams application

[adinastoll]

Pull Request Template

What are you trying to address

Contributing with a new guidance based on previous engagement on how to write UI tests for a custom Teams application.

Checklist

• Changes follow the repo structure and land in the appropriate folder and section
• No confidential information
• No duplicated content
• Labeled appropriately
• Added 2 reviewers
• No lint errors
• No lint check errors related to your changes

Note: You may see link check errors on pages you have not touched. This is normal, and due to either broken links or sites that reject link checker bots. The reviewer will help you get to a green state on these.

[benjguin]

The content looks good to me.

A few remarks:

1/ Maybe the step by step instructions are too detailed for the playbook and may generate significant maintenance work of this page over time.
I'm not managing the playbook content, so I'm not sure.

2/ Maybe a chapter or a paragraph in the Overview should summarize the findings. I think of:

• testing in Web Browser is simpler than on a native app
• Testing in a local Windows box is more stable than in a CICD that involves a CICD agent plus a VM in VM for the emulator
• Testing in a Teams app in a native app is hard
  • you are testing an app in Teams App, not the Teams App for which you don't have the APK. Frameworks expoct you to test the app for which you have the APK
  • it requires the installation of the app which is hard to automate because it requires a Google account to access the Play store

Things of that level

[adinastoll]

@benjguin Thank you for the review! :) Based on your suggestion, I added a sub-chapter in Overview to highlight the learnings. Thanks for the suggestion!

I'll keep the step by steps until further feedback from Playbook maintainers, though your point is really valid. I might keep just the aspects which are relevant to Teams (such as choosing a device with Play Store enabled, else Teams can't be installed etc)

[TessFerrandez]

Great content... I have added some language suggestions and general formatting

[adinastoll]

Great content... I have added some language suggestions and general formatting

Thank you @TessFerrandez for your review! I have addressed the comments. :)

[TessFerrandez]

@shiranr or @tompaana could one of you review this?

[shiranr]

Great content! thank you for contributing :)
Left couple of comments.

[adinastoll]

Great content! thank you for contributing :) Left couple of comments.

Thank you for reviewing it, @shiranr. I have addressed all your comments! Please have a look.

[shiranr]

LGTM! thanks