Confluence iFrame integration

Support
1

Hi everyone,

in TestRail, we used an iFrame to display test status information directly in Confluence. We are currently trying to achieve something similar with Testiny, but the iFrame approach does not seem to work.

Our goal is to provide project stakeholders with a current overview of the test status directly within Confluence, while access remains limited to authorized users.

Is there any way to display Testiny data in Confluence?

If not, has anyone found an alternative solution to display Testiny information in Confluence?

Thanks in advance!

Kevin

1 Answer

1
2

Hi and welcome to the Testiny forum!

Are you trying to show part of the Testiny app inside an iframe? The Testiny CSP does not allow that for security reasons.

What you could do instead is create your own little website/iframe that accesses the Testiny API and shows specific information.
Be sure to use a dedicated viewer account and/or dedicated viewer-only API key for that.
And also make sure to not let the API key leak into your iframe.

I’m wondering how you did the user authentication before, so where did you store the user credentials to log into your test management account?

Best regards,
Alex

Hi Alex, thank you so much! Thanks for the quick answer and for explaining the restriction. On authentication: The TestRail iframe relied on the viewer’s own TestRail login, so only users with TestRail access could see the status. Our plan is to use Claude for this: a Claude task would read the status every few hours via MCP server, using a viewer-only API key, and write a short summary into the page. That way nothing is embedded and the key never reaches the browser. Does that sound like a reasonable approach to you, or is there anything we should watch out for? Best regards Kevin

 –

Yes, the MCP update is definitely doable. The "rely on viewer's own login" would also be possible, even simpler, because then you would only need the Testiny API calls and show the returned data (the authentication reusing an existing Testiony session) - so completely stateless, but you'd need a Testiny seat per user. Best regards, Alex

 –