Closed Bug 1620425 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 22105 - Added Badging API Web Platform Tests.

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox76 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla76
Tracking Flags:
Tracking Status
firefox76 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Chris Mumford <cmumford@chromium.org> wrote:

Added Badging API Web Platform Tests.

The Badging API is a new API
allowing the setting of application/document badges. This change
converts the Badging API web tests into Web Platform Tests.

Bug: 1051684
Change-Id: I61e29b8f197a754fea489ebb2d0dcd41484f6cf4
Reviewed-on: https://chromium-review.googlesource.com/2088297
WPT-Export-Revision: 1d14be0e91785c1b3f1c2bfc9e519aac881f3d4b

CI Results

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

Total 49 tests

Status Summary

Firefox

OK : 2
PASS: 47
FAIL: 18

Chrome

OK : 2
PASS: 18

Safari

OK : 2
FAIL: 18

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/badging/badge-error.https.html
Negative infinity: FAIL (Chrome: PASS, Safari: FAIL)
NaN: FAIL (Chrome: PASS, Safari: FAIL)
Positive infinity: FAIL (Chrome: PASS, Safari: FAIL)
Negative value not allowed: FAIL (Chrome: PASS, Safari: FAIL)
Cannot convert to long: object: FAIL (Chrome: PASS, Safari: FAIL)
Value too large (2^53): FAIL (Chrome: PASS, Safari: FAIL)
Cannot convert to long: "Foo": FAIL (Chrome: PASS, Safari: FAIL)
/badging/badge-success.https.html
No parameter should show a flag with no numeric value.: FAIL (Chrome: PASS, Safari: FAIL)
Set to zero should clear the badge.: FAIL (Chrome: PASS, Safari: FAIL)
Setting to true should display a value of 1.: FAIL (Chrome: PASS, Safari: FAIL)
Setting to null should clear the badge.: FAIL (Chrome: PASS, Safari: FAIL)
Setting to false should clear the badge.: FAIL (Chrome: PASS, Safari: FAIL)
undefined should show a flag with no numeric value.: FAIL (Chrome: PASS, Safari: FAIL)
Maximum allowed value (2^53 - 1) should display saturated value: '99+'.: FAIL (Chrome: PASS, Safari: FAIL)
Non-whole number should round down to nearest integer (10).: FAIL (Chrome: PASS, Safari: FAIL)
Setting to the string '3' should display a value of 3.: FAIL (Chrome: PASS, Safari: FAIL)
An integer value of 3 should show the badge vale 3.: FAIL (Chrome: PASS, Safari: FAIL)
Should clear the badge.: FAIL (Chrome: PASS, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5e1a2750b1ba
[wpt PR 22105] - Added Badging API Web Platform Tests., a=testonly
https://hg.mozilla.org/integration/autoland/rev/ea8ba3f9cf95
[wpt PR 22105] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/5e1a2750b1ba
https://hg.mozilla.org/mozilla-central/rev/ea8ba3f9cf95

Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox76: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in before you can comment on or make changes to this bug.