1380546 - (paymentrequest-wpt) [meta] Pass web platform tests of Payment Request API

Status: NEW

(Core :: DOM: Web Payments, enhancement, P2)

Description

[Ben Tian (inactive)]

Meta bug to track web platform test bugs of Payment Request API

Comment 1

[Ben Tian (inactive)]

Depend on 'allowpaymentrequest' and basic card implementation bugs.

Comment 2

[Ben Tian (inactive)]

Summarize current status as following. Note each test may include several test cases.

=== Not All-Passed Tests ===
- tests under allowpaymentrequest/ (Bug 1318988 and Bug 1382120)
- payment-request-canmakepayment-method.https.html (Bug 1375345)
- payment-request-show-method.https.html (Bug 1379892)
- payment-request-constructor.https.html (Bug 1368949)
- payment-request-response-id.html (requires UI to test)
- Feature policy tests (low priority for irrelevant to Payment Request API itself)
  > payment-allowed-by-feature-policy-attribute-redirect-on-load.https.sub.html
  > payment-allowed-by-feature-policy-attribute.https.sub.html
  > payment-allowed-by-feature-policy.https.sub.html
  > payment-default-feature-policy.https.sub.html
  > payment-disabled-by-feature-policy.https.sub.html

=== Fixed Test Failure ===
- some failures in payment-request-constructor.https.html (Bug 1367694)
- payment-request-id.https.html (Bug 1380211)
- payment-request-onshippingaddresschange-attribute.https.html &
  payment-request-onshippingoptionchange-attribute.https.html (Bug 1379925)
- payment-request-update-event-constructor.https.html (Bug 1380552)
- payment-request-update-event-updatewith-method.https.html (Bug 1380553)


=== How to Test ===
1) Open the latest Nightly
2) Enable 'dom.payments.request.enabled' in about:config
3) Go to https://w3c-test.org/payment-request/ and click on tests
* Note payment-request-constructor-crash.https.html takes longer time for it tests with very long string/large array

Comment 3

[Ben Tian (inactive)]

(In reply to Ben Tian [:btian] from comment #2)
> Summarize current status as following. Note each test may include several
> test cases.

The full list is in https://w3c-test.org/payment-request/
Should've moved [How to Test] to the beginning.

=== How to Test ===
1) Open the latest Nightly
2) Enable 'dom.payments.request.enabled' in about:config
3) Go to https://w3c-test.org/payment-request/ and click on tests
* Note payment-request-constructor-crash.https.html takes longer time for it tests with very long string/large array

> === Not All-Passed Tests ===
> - tests under allowpaymentrequest/ (Bug 1318988 and Bug 1382120)
> - payment-request-canmakepayment-method.https.html (Bug 1375345)
> - payment-request-show-method.https.html (Bug 1379892)
> - payment-request-constructor.https.html (Bug 1368949)
> - payment-request-response-id.html (requires UI to test)
> - Feature policy tests (low priority for irrelevant to Payment Request API
> itself)
>   >
> payment-allowed-by-feature-policy-attribute-redirect-on-load.https.sub.html
>   > payment-allowed-by-feature-policy-attribute.https.sub.html
>   > payment-allowed-by-feature-policy.https.sub.html
>   > payment-default-feature-policy.https.sub.html
>   > payment-disabled-by-feature-policy.https.sub.html
> 
> === Fixed Test Failure ===
> - some failures in payment-request-constructor.https.html (Bug 1367694)
> - payment-request-id.https.html (Bug 1380211)
> - payment-request-onshippingaddresschange-attribute.https.html &
>   payment-request-onshippingoptionchange-attribute.https.html (Bug 1379925)
> - payment-request-update-event-constructor.https.html (Bug 1380552)
> - payment-request-update-event-updatewith-method.https.html (Bug 1380553)

Comment 4

[Eden Chuang[:edenchuang]]

I am going to use this bug to address PaymentRequest web-platform-test issues.

Setting most of them as expected pass and running them automatically.