Conversation
Marks applied to fixtures have no effect and are now an error in pytest 9 (PytestRemovedIn9Warning). All test functions using this fixture already have their own @pytest.mark.cdn decorator.
Newer Selenium enforces W3C WebDriver spec compliance, rejecting vendor-specific capabilities (avoidProxy, tags) at the top level. These must be nested under sauce:options.
For https://github.com/mozilla/bedrock/actions/runs/21957292026/job/63424850468, it looks like the submit button was clickable but timed out. It might be caused by https://github.com/mozmeao/springfield/blob/main/media/js/newsletter/form-utils.es6.js#L90. If we are using |
Did you mean to link to the springfield repo there? |
Oops, I meant to link the same file in |
|
Would you have any time to try fixing it? (I'll update the merge conflict
around the CDN tests first)
|
|
I can look into this the second half of my day 👍 |
This catches up with straggling version bumps that historically were painful around pytest-selenium, but I figured it was time to bite the bullet
And.... integration tests are... seemingly happy, but have some error annotations, oddly: https://github.com/mozilla/bedrock/actions/runs/21957292026 and https://github.com/mozilla/bedrock/actions/runs/21959245804 - are these false positives or tolerable negatives @maureenlholland @wen-2018 ?