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

Allow the whole report to be contrained to a specifc time range #138

Closed
damies13 opened this issue Mar 14, 2023 · 1 comment
Closed

Allow the whole report to be contrained to a specifc time range #138

damies13 opened this issue Mar 14, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request Reporter Issue Affects the Manager (this is a planned component)
Milestone

Comments

@damies13
Copy link
Owner

Is your feature request related to a problem? Please describe.
It's would be useful to have the report only show the data from a specific part of the test, useful for reporting on problems or reporting on only the steady state part of a test run (filtering out the ramp-up and ramp-down)

Describe the solution you'd like
On the Global Report Settings screen, you'll see the start and end time are displayed, change those to input fields so you could adjust the time period for the whole report, then the SQL that generated the report data needs to take in this time range.

Additional context
This issue came as from a suggestion in Issue #120 --> #120 (comment)

@damies13 damies13 added enhancement New feature or request Reporter Issue Affects the Manager (this is a planned component) labels Mar 14, 2023
@damies13 damies13 added this to the v1.3.0 milestone Mar 10, 2024
@damies13 damies13 self-assigned this Apr 1, 2024
damies13 added a commit that referenced this issue Apr 22, 2024
The start time and end time are now input fields that can have the time modified, the updated time is converted from formatted value to epoch seconds and saved to report.
value saved to report is read (uses original value if no value in report file) and all graphs and data tables now use the value that's saved to the report file
Issue #138

Now to handle odd inputs better
damies13 added a commit that referenced this issue Apr 25, 2024
Plus some restructure of existing test cases for Reporter and some test data for Issue new test case
damies13 added a commit that referenced this issue Apr 25, 2024
damies13 added a commit that referenced this issue Apr 25, 2024
damies13 added a commit that referenced this issue Apr 25, 2024
damies13 added a commit that referenced this issue Apr 27, 2024
no wonder it didn't work - Issue #138
damies13 added a commit that referenced this issue Apr 27, 2024
damies13 added a commit that referenced this issue Apr 27, 2024
damies13 added a commit that referenced this issue Apr 27, 2024
damies13 added a commit that referenced this issue Apr 28, 2024
damies13 added a commit that referenced this issue Apr 28, 2024
damies13 added a commit that referenced this issue Apr 28, 2024
Also robots graph for Ubuntu and confidence level for Windows
Issue #138
damies13 added a commit that referenced this issue Apr 28, 2024
Also robots graph for Ubuntu and confidence level for Windows
Issue #138
damies13 added a commit that referenced this issue Apr 28, 2024
damies13 added a commit that referenced this issue Apr 28, 2024
damies13 added a commit that referenced this issue Apr 28, 2024
@damies13
Copy link
Owner Author

Feature done and test cases for reporter all passing, merged into release branch v1.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Reporter Issue Affects the Manager (this is a planned component)
Projects
None yet
Development

No branches or pull requests

1 participant