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

Keyword execution time analysis tool #135

Closed
Muusssi opened this issue Mar 8, 2021 · 1 comment · Fixed by #136
Closed

Keyword execution time analysis tool #135

Muusssi opened this issue Mar 8, 2021 · 1 comment · Fixed by #136
Labels
enhancement New feature or request

Comments

@Muusssi
Copy link
Member

Muusssi commented Mar 8, 2021

Is your feature request related to a problem? Please describe.
TestArchiver collects statistics of the keywords and their running time and Currently there is no ways to browse that data in the tool.

Describe the solution you'd like
A simple list of the keywords in a build and aggregated data from the keywords statistics table in the test archive. The table should be ordered by how much of the total execution time was spent execution the keyword in descending order.

Describe alternatives you've considered
I did some prototyping with the keyword statistics data and this table was the most generic but almost always interesting and meaningful analysis of the data. Other more detailed or complex prototypes would have required more qualifiers for the included keywords and made the feature less generic and much more complex.

Additional context
This tool is supposed to be released for RoboCon and its prototype will be demoed in a lightning talk.

@Muusssi Muusssi added the enhancement New feature or request label Mar 8, 2021
@Muusssi Muusssi linked a pull request Mar 8, 2021 that will close this issue
@Muusssi
Copy link
Member Author

Muusssi commented Mar 8, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants