Closed Bug 1761838 Opened 9 months ago Closed 8 months ago

[wpt-sync] Sync PR 33391 - [basic-card] Migrate WPTs that use basic-card identifier

Categories

(Core :: DOM: Web Payments, task, P4)

task

Tracking

()

RESOLVED FIXED
100 Branch
Tracking Status
firefox100 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 33391 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/33391
Details from upstream follow.

Nick Burris <nburris@chromium.org> wrote:

[basic-card] Migrate WPTs that use basic-card identifier

With basic card now disabled and soon to be removed, migrate web
platform tests that test the payment method identifier syntax to use
secure-payment-confirmation instead of basic-card. These tests pass
either way, this is just to refresh the test data to a current feature.

The merchant-validation test is also updated, in addition to the
similar PMI validation change, it is updated to use an example URL
payment method.

Bug: 1209835
Change-Id: I109e9063720c21d10c5c0af1f765d553eaadeb83
Reviewed-on: https://chromium-review.googlesource.com/3556267
WPT-Export-Revision: 16d9588b8ddb10d2e4a96228d28b3c8c2aca4803

Component: web-platform-tests → DOM: Web Payments
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 3 tests and 4 subtests

Status Summary

Firefox

OK : 3
FAIL: 19

Chrome

OK : 3
PASS: 19

Safari

OK : 3
PASS: 18
FAIL: 1

Links

GitHub PR Head
GitHub PR Base

Details

Firefox-only Failures

/merchant-validation/constructor.tentative.https.html
MerchantValidationEvent can be constructed in secure-context.: FAIL
MerchantValidationEvent can be constructed with an EventInitDict, even if not trusted.: FAIL
MerchantValidationEvent can be dispatched, even if not trusted.: FAIL
Must have a validationURL IDL attribute, which is initialized with to the validationURL dictionary value.: FAIL
Must throw TypeError if initialized with an invalid URL.: FAIL
Relative validationURLs use the document as the base.: FAIL
Must have a methodName IDL attribute, which is initialized with to the methodName dictionary value.: FAIL
When no methodName is passed, methodName attribute defaults to the empty string: FAIL
MerchantValidationEvent can be constructed with valid PMIs: FAIL
MerchantValidationEvent can't be constructed with invalid PMIs: FAIL
/payment-method-id/payment-request-ctor-pmi-handling.https.sub.html
Must support valid standard URL PMIs: FAIL
Must not throw on syntactically valid standardized payment method identifiers, even if they are not supported: FAIL
Must throw on syntactically invalid standardized payment method identifiers: FAIL
Constructor MUST throw if given an invalid URL-based payment method identifier: FAIL
/payment-request/payment-request-ctor-pmi-handling.https.sub.html
Must support valid standard URL PMIs: FAIL
Must not throw on syntactically valid standardized payment method identifiers, even if they are not supported: FAIL
Must throw on syntactically invalid standardized payment method identifiers: FAIL
Constructor MUST throw if given an invalid URL-based payment method identifier: FAIL

New Tests That Don't Pass

/merchant-validation/constructor.tentative.https.html
MerchantValidationEvent can be constructed in secure-context.: FAIL (Chrome: PASS, Safari: PASS)
MerchantValidationEvent can be constructed with an EventInitDict, even if not trusted.: FAIL (Chrome: PASS, Safari: PASS)
MerchantValidationEvent can be dispatched, even if not trusted.: FAIL (Chrome: PASS, Safari: PASS)
Must have a validationURL IDL attribute, which is initialized with to the validationURL dictionary value.: FAIL (Chrome: PASS, Safari: PASS)
Must throw TypeError if initialized with an invalid URL.: FAIL (Chrome: PASS, Safari: PASS)
Relative validationURLs use the document as the base.: FAIL (Chrome: PASS, Safari: PASS)
Relative validationURLs use the document.baseURI as the base.: FAIL (Chrome: PASS, Safari: FAIL)
Must have a methodName IDL attribute, which is initialized with to the methodName dictionary value.: FAIL (Chrome: PASS, Safari: PASS)
When no methodName is passed, methodName attribute defaults to the empty string: FAIL (Chrome: PASS, Safari: PASS)
MerchantValidationEvent can be constructed with valid PMIs: FAIL (Chrome: PASS, Safari: PASS)
MerchantValidationEvent can't be constructed with invalid PMIs: FAIL (Chrome: PASS, Safari: PASS)
/payment-method-id/payment-request-ctor-pmi-handling.https.sub.html
Must support valid standard URL PMIs: FAIL (Chrome: PASS, Safari: PASS)
Must not throw on syntactically valid standardized payment method identifiers, even if they are not supported: FAIL (Chrome: PASS, Safari: PASS)
Must throw on syntactically invalid standardized payment method identifiers: FAIL (Chrome: PASS, Safari: PASS)
Constructor MUST throw if given an invalid URL-based payment method identifier: FAIL (Chrome: PASS, Safari: PASS)
/payment-request/payment-request-ctor-pmi-handling.https.sub.html
Must support valid standard URL PMIs: FAIL (Chrome: PASS, Safari: PASS)
Must not throw on syntactically valid standardized payment method identifiers, even if they are not supported: FAIL (Chrome: PASS, Safari: PASS)
Must throw on syntactically invalid standardized payment method identifiers: FAIL (Chrome: PASS, Safari: PASS)
Constructor MUST throw if given an invalid URL-based payment method identifier: FAIL (Chrome: PASS, Safari: PASS)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/df04f5cc3803
[wpt PR 33391] - [basic-card] Migrate WPTs that use basic-card identifier, a=testonly
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in before you can comment on or make changes to this bug.