mv payments policy tests to /feature-policy/

[marcoscaceres]

• closes Cross-origin Payment Request in Payment Allowed By Feature Policy #6899, Payment allowed-by-feature-policy test #6812

[wpt-pr-bot]

There are no owners for this pull request. Please reach out on W3C's irc server (irc.w3.org, port 6665) on channel #testing (web client) to get help with this. Thank you!

[w3c-bots]

Build PASSED

Started: 2017-09-12 01:34:22
Finished: 2017-09-12 01:35:03

Failing Jobs

• MicrosoftEdge:14.14393

Unstable Results

Browser: "Microsoftedge 14.14393" (failures allowed)

View in: WPT PR Status | TravisCI

Test	Subtest	Results	Messages
/feature-policy/payment-allowed-by-feature-policy-attribute.https.sub.html		OK: 6
	Feature policy "payment" can be enabled in cross-origin iframe using allow="payment" attribute	FAIL: 6	Unable to get property 'concat' of undefined or null reference
	Feature policy "payment" can be enabled in same-origin iframe using allow="payment" attribute	FAIL: 6	Unable to get property 'concat' of undefined or null reference
/feature-policy/payment-allowed-by-feature-policy-attribute-redirect-on-load.https.sub.html		OK: 6
	Feature-Policy allow="payment" allowpaymentrequest=true allows same-origin relocation.	FAIL: 6	Unable to get property 'concat' of undefined or null reference
	Feature-Policy allow="payment" allowpaymentrequest=true disallows cross-origin relocation.	FAIL: 6	Unable to get property 'concat' of undefined or null reference
	Feature-Policy allow="payment" allows same-origin relocation.	FAIL: 6	Unable to get property 'concat' of undefined or null reference
	Feature-Policy allow="payment" disallows cross-origin relocation.	FAIL: 6	Unable to get property 'concat' of undefined or null reference
/feature-policy/payment-allowed-by-feature-policy.https.sub.html		TIMEOUT: 6
/feature-policy/payment-default-feature-policy.https.sub.html		TIMEOUT: 6
/feature-policy/payment-disabled-by-feature-policy.https.sub.html		TIMEOUT: 6

[clelland]

If this pattern repeats for a large number of other APIs, we may want to move this into /feature-policy/features/payment-request/ or something similar, but I don't think there's any need to impose that kind of structure yet.

[clelland]

(Also, I may not be allowed to approve the change that makes me an owner -- it might have to be done in two steps, or someone else may need to approve this one)

[marcoscaceres]

cc @sideshowbarker for super powers.

[marcoscaceres]

If this pattern repeats for a large number of other APIs, we may want to move this into /feature-policy/features/payment-request/ or something similar, but I don't think there's any need to impose that kind of structure yet.

Agree. That would be nice. I'm not a huge fan of the tests with the massively long filenames. Prefer they were in nicely organized folders.