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] Expand testing for non-default space report generation #72875

Closed
poffdeluxe opened this issue Jul 22, 2020 · 4 comments · Fixed by #76053
Closed

[Reporting] Expand testing for non-default space report generation #72875

poffdeluxe opened this issue Jul 22, 2020 · 4 comments · Fixed by #76053
Labels
Feature:Reporting:Framework Reporting issues pertaining to the overall framework needs-team Issues missing a team label

Comments

@poffdeluxe
Copy link
Contributor

After #72475 popped up during the testing spike, it might be helpful to include some new functional/automated tests that explicitly test the non-default space case when generating both PDF and PNG reports.

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@poffdeluxe
Copy link
Contributor Author

Adding some automated testing for generating pdf reports from Canvas workpads is something that the @elastic/kibana-canvas team and I can definitely help with

@tsullivan
Copy link
Member

@poffdeluxe please go ahead and add some automated testing for this requirement. The @elastic/kibana-reporting-services team is backlogged at the moment. So, if you can offer to help it is much appreciated!

@tsullivan
Copy link
Member

PR on the way: #76053

@sophiec20 sophiec20 added Feature:Reporting:Framework Reporting issues pertaining to the overall framework and removed (Deprecated) Team:Reporting Services labels Aug 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Reporting:Framework Reporting issues pertaining to the overall framework needs-team Issues missing a team label
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants