Google Git
Sign in
chromium / external / w3c / web-platform-tests / master / . / reporting
tree: eaa641c79b6a466193d1f06173ef1a2a3889684e [path history] [tgz]
  1. resources/
  2. bufferSize.html
  3. crashReport-test.html
  4. cross-origin-report-no-credentials.https.sub.html
  5. cross-origin-report-no-credentials.https.sub.html.sub.headers
  6. cross-origin-reports-isolated.https.sub.html
  7. cross-origin-reports-isolated.https.sub.html.sub.headers
  8. cross-origin-same-site-credentials.https.sub.html
  9. disconnect.html
  10. document-reporting-bypass-report-to.https.sub.html
  11. document-reporting-bypass-report-to.https.sub.html.sub.headers
  12. document-reporting-default-endpoint.https.sub.html
  13. document-reporting-default-endpoint.https.sub.html.sub.headers
  14. document-reporting-destroy-after-document-close.https.sub.html
  15. document-reporting-named-endpoints.https.sub.html
  16. document-reporting-named-endpoints.https.sub.html.sub.headers
  17. document-reporting-not-batch-different-document.https.html
  18. document-reporting-override-endpoint.https.sub.html
  19. document-reporting-override-endpoint.https.sub.html.sub.headers
  20. document-reporting-path-absolute.https.sub.html
  21. document-reporting-path-absolute.https.sub.html.sub.headers
  22. generateTestReport-honors-endpoint.https.sub.html
  23. generateTestReport-honors-endpoint.https.sub.html.sub.headers
  24. generateTestReport.html
  25. idlharness.any.js
  26. META.yml
  27. nestedReport.html
  28. order.html
  29. README.md
  30. reporting-api-honors-limits.https.sub.html
  31. reporting-api-honors-limits.https.sub.html.sub.headers
  32. reporting-isolated-across-navigations.https.sub.html
  33. same-origin-cross-site-credentials.https.sub.html
  34. same-origin-report-credentials.https.sub.html
  35. same-origin-report-credentials.https.sub.html.sub.headers
  36. same-origin-same-site-credentials.https.sub.html
  37. WEB_FEATURES.yml
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.