Closed Bug 1619864 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 22079 - [WPT/common/security-features] Add default spec.src.json

Categories

(Core :: DOM: Security, task, P4)

Product:
Core
Component:
DOM: Security
Type:
task

Tracking

()

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

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream][domsecurity-backlog])

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

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

Hiroshige Hayashizaki <hiroshige@chromium.org> wrote:

[WPT/common/security-features] Add default spec.src.json

There were multiple spec.src.json for each project directories
that have many things in common, e.g. lists of subresources,
source contexts, etc.

This CL introduces common/security-features/tools/spec.src.json
that works as the default spec.src.json, and moves
common things into the default spec.src.json.
By doing this, we can ensure uniform test coverage across projects
(e.g. the same set of subresource requests are covered in
referrer-policy and mixed-content tests) more easily.

To keep the generated tests the same, this CL adds
exclusion rules named "... not yet tested".

This CL doesn't affect test behavior nor generated results.

Bug: 906850
Change-Id: Id06bc6e311a482f50531cd36e6da57b2e6df22ec

Reviewed-on: https://chromium-review.googlesource.com/2049953
WPT-Export-Revision: 23e35961c65bd1cd7a3998b037621a07758916af

Component: web-platform-tests → DOM: Security
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Test result changes from PR not available.
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ca4867a91257
[wpt PR 22079] - [WPT/common/security-features] Add default spec.src.json, a=testonly

https://hg.mozilla.org/mozilla-central/rev/ca4867a91257

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.