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

Add support for scheduling reports using ReportTemplates #458

Open
ColeHiggins2 opened this issue Feb 24, 2020 · 3 comments
Open

Add support for scheduling reports using ReportTemplates #458

ColeHiggins2 opened this issue Feb 24, 2020 · 3 comments
Labels
enhancement New feature or request medium Medium priority issue view Issues related to Views coverage

Comments

@ColeHiggins2
Copy link
Member

ColeHiggins2 commented Feb 24, 2020

I do not believe it is possible to schedule a report using airgun. session.reporttemplate.schedule() is not currently supported. Additionally, Session.reporttemplate.generate with the specified field "Generate at" is also not supported. I think either a scheduling method needs to be created or the functionality needs to be added to the existing reporttemplate.generate() call.

This is needed to test Entitlements reports under Report Templates

@mirekdlugosz mirekdlugosz added enhancement New feature or request medium Medium priority issue view Issues related to Views coverage labels Feb 24, 2020
@mirekdlugosz
Copy link
Contributor

Yes, there is no support for "Generate at" field.

Without digging much, I'd say we should use generate() instead of creating new entity method. It already opens relevant screen.

One possible problem might be that generate() unconditionally waits for raport to be generated. I don't know if it will handle scheduled report. If it does, it might not make sense to block execution of test script while waiting for report. So generate() should probably get new argument, say sync, which would indicate if execution should be blocked or not. When not blocked, we should return something that makes it easy to come back to this particular report later on.

Another thing is that "generate at" field uses some non-standard popup calendar. We have support for calendar widgets in airgun/widgets.py: DateTime and DatePickerInput. From what I see, these two are not the same as calendar used in reports (most likely another case of Satellite moving slowly to react). It might be possible to use one of these two classes, maybe subclass it. Either way, I would recommend looking where these two are used and if they even still work.

@JacobCallahan
Copy link
Member

@mirekdlugosz @mshriver do either of you know who would be the best option to get this implemented?

@lhellebr
Copy link
Contributor

I'll look into it when I have time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request medium Medium priority issue view Issues related to Views coverage
Projects
None yet
Development

No branches or pull requests

4 participants