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 more detailed WPT test coverage for stopping behavior. #33815

Merged
merged 1 commit into from Apr 28, 2022

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Apr 27, 2022

The added tests aim to cover:

  • When transceiver.recevier.track should or should not end.
  • When transceiver is stopped locally versus remotely.
  • When the transceiver is "stopping" or "stopped".
  • When transceiver is stopped due to being removed in a rollback versus
    being rolled back without being removed.

The -expected.txt file reflects https://crbug.com/1315611 being fixed,
but the following issues have not been fixed yet which FAIL:

// Test coverage for the following issues:

Bug: 1315611, 1319902, 1319911, 1319913, 1319924
Change-Id: I8ad97221f5d2171384e8c7be32eaabd9811ba8f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3609997
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/main@{#997067}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-3609997 branch 2 times, most recently from 32389c5 to 66b592d Compare April 28, 2022 06:12
The added tests aim to cover:
- When transceiver.recevier.track should or should not end.
- When transceiver is stopped locally versus remotely.
- When the transceiver is "stopping" or "stopped".
- When transceiver is stopped due to being removed in a rollback versus
  being rolled back without being removed.

The -expected.txt file reflects https://crbug.com/1315611 being fixed,
but the following issues have not been fixed yet which FAIL:
- https://crbug.com/1319913: direction is not updated to "stopped" if
  transceiver is stopped remotely.
- https://crbug.com/1319911: currentDirection is not updated to
  "stopped" when already "stopping" and answer removes the transceiver.

// Test coverage for the following issues:

Bug: 1315611, 1319902, 1319911, 1319913, 1319924
Change-Id: I8ad97221f5d2171384e8c7be32eaabd9811ba8f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3609997
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/main@{#997067}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants