Google Git
Sign in
chromium / external / github.com / web-platform-tests / wpt / refs/tags/merge_pr_34226 / . / reporting
tree: a96505e3a83ed01040adf36a0842cc7a16389746 [path history] [tgz]
  1. resources/
  2. bufferSize.html
  3. cross-origin-report-no-credentials.https.sub.html
  4. cross-origin-report-no-credentials.https.sub.html.sub.headers
  5. cross-origin-reports-isolated.https.sub.html
  6. cross-origin-reports-isolated.https.sub.html.sub.headers
  7. cross-origin-same-site-credentials.https.sub.html
  8. disconnect.html
  9. document-reporting-bypass-report-to.https.sub.html
  10. document-reporting-bypass-report-to.https.sub.html.sub.headers
  11. document-reporting-default-endpoint.https.sub.html
  12. document-reporting-default-endpoint.https.sub.html.sub.headers
  13. document-reporting-destroy-after-document-close.https.sub.html
  14. document-reporting-named-endpoints.https.sub.html
  15. document-reporting-named-endpoints.https.sub.html.sub.headers
  16. document-reporting-not-batch-different-document.https.html
  17. document-reporting-override-endpoint.https.sub.html
  18. document-reporting-override-endpoint.https.sub.html.sub.headers
  19. document-reporting-path-absolute.https.sub.html
  20. document-reporting-path-absolute.https.sub.html.sub.headers
  21. generateTestReport.html
  22. idlharness.any.js
  23. META.yml
  24. nestedReport.html
  25. order.html
  26. README.md
  27. reporting-isolated-across-navigations.https.sub.html
  28. same-origin-cross-site-credentials.https.sub.html
  29. same-origin-report-credentials.https.sub.html
  30. same-origin-report-credentials.https.sub.html.sub.headers
  31. same-origin-same-site-credentials.https.sub.html
reporting/README.md

Tests for the Reporting API.

The tests in this directory validate the generic functionaity of the Reporting API. Since reports are not actually generated by that specification, these tests occasionally make use of other integrations, like CSP or Permissions Policy.

Testing integration with the Reporting API

More comprehensive tests for other specifications' generated reports should be in those specs' respective directories.

There are two general methods of testing reporting integration:

  • The simpler is with the ReportingObserver interface, generating reports within a document and reading them from script running in that document.
  • For reports which cannot be observed from a document, there is a reporting collector provided which can receive reports sent over HTTP and then serve them in response to queries from the test script. See resources/README.md for details.