Added a Test for Teams app testing. #68
Conversation
WSEAutomationTests
requested review from
Copilot,
frankwbd,
rainalodha and
shravyasirivoru
There was a problem hiding this comment.
Pull Request Overview
This PR adds automated end-to-end testing capabilities for Microsoft Teams application functionality. The new test verifies Teams meeting workflow including camera and audio controls, performance monitoring, and device power state testing.
Key changes:
- New Teams test automation framework with meeting join/leave functionality
- UI automation handlers for Teams camera and audio controls
- Enhanced element finding utilities to support Teams app automation
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| E2E/TeamsTest.ps1 | Main test script that orchestrates Teams e2e testing across different power states |
| E2E/Library/TeamsAppHandlers.ps1 | Teams-specific automation functions for meeting controls and camera/audio management |
| E2E/Library/FindClickableElement.ps1 | Enhanced UI element finding with process ID support and improved conditional logic |
| E2E/CheckInTest/Helper-library.ps1 | Added import for Teams handlers library |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
E2E/TeamsTest.ps1
Outdated
| Write-Output "Entering CheckServiceState function" | ||
| CheckServiceState 'Windows Camera Frame Server' | ||
|
|
||
| # Strating to collect Traces |
There was a problem hiding this comment.
Typo in comment: 'Strating' should be 'Starting'.
| # Strating to collect Traces | |
| # Starting to collect Traces |
| { | ||
| Write-Log -Message "Entering Start-TeamsMeeting function" -IsOutput | ||
|
|
||
| # Launch the Teams app with the meeting link | ||
| Start-Process "https://teams.live.com/meet/9393388815307?p=DjwPrJ9iFrjS0pdlyT" |
There was a problem hiding this comment.
The Teams meeting link is hardcoded. Consider making this configurable through a parameter or configuration file to improve maintainability and reusability.
| { | |
| Write-Log -Message "Entering Start-TeamsMeeting function" -IsOutput | |
| # Launch the Teams app with the meeting link | |
| Start-Process "https://teams.live.com/meet/9393388815307?p=DjwPrJ9iFrjS0pdlyT" | |
| ( | |
| [Parameter(Mandatory=$true)] | |
| [string]$teamsMeetingLink | |
| ) | |
| { | |
| Write-Log -Message "Entering Start-TeamsMeeting function" -IsOutput | |
| # Launch the Teams app with the meeting link | |
| Start-Process $teamsMeetingLink |
E2E/Library/TeamsAppHandlers.ps1
Outdated
| } | ||
| else | ||
| { | ||
| FindAndClick -uiEle $uiTeams -proptyNme "Turn camera on" |
There was a problem hiding this comment.
Variable '$uiTeams' is not defined in these functions. Should use the parameter '$uiEle' instead.
E2E/Library/TeamsAppHandlers.ps1
Outdated
| } | ||
| else | ||
| { | ||
| FindAndClick -uiEle $uiTeams -proptyNme "Unmute mic" |
There was a problem hiding this comment.
Variable '$uiTeams' is not defined in these functions. Should use the parameter '$uiEle' instead.
|
Could you share the results of test run please? |
WSEAutomationTests
requested review from
ganeshsurada
and removed request for
aastitva and
frankwbd
What changed?
Added a new test case for Teams App testing.
Why changed?
We didn't have this test scenario automated in our test suite earlier.
How did you test the change?
Tested successfully after signing in as MEPTesting with Teams.
Related Issues (if any):
Note: I am still testing as the same Teams link is sometime not working across all devices.