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.

Sign up for GitHub

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

Jump to bottom

Performance tests: generate .md along with each release #140

Open
MangyCoyote opened this issue May 1, 2020 · 0 comments
Open

Performance tests: generate .md along with each release #140

MangyCoyote opened this issue May 1, 2020 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request performance Performance related tasks testing Testing needs to be implemented or fixed
Milestone
later

Comments

@MangyCoyote
Copy link
Collaborator

Idea is to have a documented performance overview. Did your change break performance or has improved with respect to previous release(s)?

Execute performance tests each time if we do a release and mark it down to .md file.
Automatic way ONLY.
It can generate MD file for each test, and then we'll just add it somewhere.

Maybe should be added to build pipeline?, right after iTests.
So if you know your PullRequest has passed iTests, you could compare straight away performance.
As a "pass on error" step.
@MangyCoyote MangyCoyote added documentation Improvements or additions to documentation enhancement New feature or request testing Testing needs to be implemented or fixed performance Performance related tasks labels May 1, 2020
@MangyCoyote MangyCoyote added this to the later milestone May 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation enhancement New feature or request performance Performance related tasks testing Testing needs to be implemented or fixed
Projects
None yet
Milestone
later
Development

No branches or pull requests
1 participant
@MangyCoyote