Microsoft Teams - Host and Guest
Overview
This workflow is distinct from traditional Login Enterprise workloads. The Teams Host and Guest workflows operate synchronously and should be run in separate Tests. For example, you can start the Guest Test first, and then begin the Host Test. Since the Tests wait for events generated by each other, they will remain synchronized. If you have both set as a Continuous Test with one concurrent session, you can keep the Test Runs in sync.
Summary
This workflow involves two roles: the Host and the Guest. As these roles are designed to operate synchronously, the steps are listed in sequential order.
Host Actions:
Open Teams.
Navigate to the Calendar page in Teams.
Start a new meeting and join using the default audio/video settings.
Invite the Guest user to the meeting.
Guest Actions:
Open Teams.
Wait for the incoming Teams call notification in the lower-left corner of the desktop.
Click the notification to accept the call and join the meeting using the default audio/video settings.
Once the Guest joins, the Host:
Opens the Screen Share menu and selects an existing PowerPoint presentation window.
Waits for the specified duration while sharing the screen.
After the Host completes screen sharing:
Ends the screen share.
Leaves the meeting.
At this point, the Guest:
Waits to confirm that the Host has left the meeting.
Once confirmed, exits the meeting.
The Host script is designed with specific requirements and assumptions. It expects that a PowerPoint presentation is already running on the Host machine, which can be shared with the Guest. With minor customizations, screen sharing can be omitted or replaced with windows from other applications in the Application Group used for the respective test configuration. Lines 110–133 of the attached script address this part of the workflow.
Disclaimer
This workload is provided as-is and may require additional configuration and customization to function properly in each unique environment. For further customization through Professional Services, please consult with the Support and Services team. For more self-help information on workload crafting and implementation, refer to the Application Script Recording.