Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reporting API #8370

Open
fcarriedos opened this issue Feb 3, 2025 · 1 comment
Open

Reporting API #8370

fcarriedos opened this issue Feb 3, 2025 · 1 comment
Labels
STATE: Need clarification An issue lacks information for further research. TYPE: enhancement The accepted proposal for future implementation.

Comments

@fcarriedos
Copy link

What is your Scenario?

I am automating navigation to report Content-Security-Policy violations through the browsers' Reporting API (Edge, Chromium), so I get the CSP violations in my reporting server.

When performing the same steps manually, I see the reports appearing on the reporting server.

However when I run the exact same steps through TestCafe, reports are not sent.

What are you suggesting?

There should be a way to ensure the Reporting API is enabled in the browser when running tests, so CSP reports should be sent to my CSP server when navigating automatically with TestCafe.

What alternatives have you considered?

Manual testing, other testing frameworks...

Additional context

No response

@fcarriedos fcarriedos added the TYPE: enhancement The accepted proposal for future implementation. label Feb 3, 2025
@testcafe-need-response-bot testcafe-need-response-bot bot added the STATE: Need response An issue that requires a response or attention from the team. label Feb 3, 2025
@aleks-pro aleks-pro added the STATE: Need simple sample A simple sample is required to examine the issue. label Feb 6, 2025
Copy link

github-actions bot commented Feb 6, 2025

Thank you for submitting a bug report. We would love to help you investigate the issue. Please share a simple code example that reliably reproduces the bug. For more information, read the following article: How To Create a Minimal Working Example When You Submit an Issue. We look forward to your response.

@github-actions github-actions bot added STATE: Need clarification An issue lacks information for further research. and removed STATE: Need response An issue that requires a response or attention from the team. STATE: Need simple sample A simple sample is required to examine the issue. labels Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Need clarification An issue lacks information for further research. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

No branches or pull requests

2 participants