Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add delay and use meeting leave over end in event reporting test #1779

Merged
merged 1 commit into from
Nov 10, 2021

Commits on Nov 10, 2021

  1. Add delay and use meeting leave over end in event reporting test

    1. I am using EndMeetingStep instead of LeaveMeetingStep. When a meeting is ended the ingestion service invalidates the authorization token cache and hence any request reaching after this invalidation will result into a 403.
    2. The join and the roster check often completes very quickly in about 3-4s seconds and soon the End meeting step is triggered. Now according to logic for event ingestion from client side, we send the collected events at an interval of 5s. Thus, this explains why the request may have not got triggered and the test ends soon with also ending the meeting.
    3. The end meeting will move away from the meeting screen so this should also still send the POST request using sendBeacon but since the authorization token itself may have been invalidated those request might result in 403.
    
    To address this I am making below changes to the existing test:
    1. Use LeaveMeeting over EndMeeting step.
    2. Add a delay of 5s before leaving the meeting.
    devalevenkatesh committed Nov 10, 2021
    Configuration menu
    Copy the full SHA
    7e14010 View commit details
    Browse the repository at this point in the history