[rb] Remove fedcm test guard due to fix in chrome #16119
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
User description
🔗 Related Issues
#16118 Enables the test for the Python bindings due to the same reason as this PR
It can only be merged after the pipeline uses Chrome 140
💥 What does this PR do?
This PR re-enables the fedCM ruby binding tests that had to be skipped due to the regression added on Chrome and described here: https://issues.chromium.org/issues/425801332
🔧 Implementation Notes
This PR just removes the standard guard added to the fedCM tests
🔄 Types of changes
PR Type
Tests
Description
Remove Chrome-specific test exclusion for FedCM tests
Re-enable previously skipped Ruby binding tests
Clean up test guard after Chrome regression fix
Diagram Walkthrough
File Walkthrough
fedcm_spec.rb
Remove Chrome exclusion from FedCM tests
rb/spec/integration/selenium/webdriver/fedcm_spec.rb
exclude
parameter targeting Chrome browser