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

Run performance test on azure CI #1966

Closed
DonJayamanne opened this issue Jun 14, 2018 · 3 comments
Closed

Run performance test on azure CI #1966

DonJayamanne opened this issue Jun 14, 2018 · 3 comments
Labels
debt Covers everything internal: CI, testing, refactoring of the codebase, etc. important Issue identified as high-priority

Comments

@DonJayamanne
Copy link

A new job has been added on Travis to compare load times of the extension for 3 scenarios. We need to run these tests on VSTS as well (preferably as a separate job).

screen shot 2018-06-13 at 7 50 10 pm

screen shot 2018-06-13 at 7 50 35 pm

Note: The logs are important in this test as that's were we log the metrics.
@brettcannon brettcannon added needs PR debt Covers everything internal: CI, testing, refactoring of the codebase, etc. labels Jun 14, 2018
@DonJayamanne DonJayamanne added the P2 label Oct 2, 2018
@DonJayamanne
Copy link
Author

@d3r3kk
Please could you look into this sometime next week or so.

@d3r3kk
Copy link

d3r3kk commented Oct 2, 2018

Sure thing - let's bring it up in sprint planning.

cc: @brettcannon

@DonJayamanne
Copy link
Author

DonJayamanne commented Jun 25, 2019 •
edited
Loading

Upgrading to P1, this used to be done, we've added the code into CI, but the tests are NOT running.
Should be able to easily automate via the UI Tests #4692

P1 = because we cannot regress in terms of performance, and we used to do this on the older CI

@DonJayamanne DonJayamanne added important Issue identified as high-priority and removed P2 labels Jun 25, 2019
@DonJayamanne DonJayamanne changed the title Run performance test on VSTS Run performance test on azure CI Jul 17, 2019
@ghost ghost removed the needs PR label Jul 17, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jul 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
debt Covers everything internal: CI, testing, refactoring of the codebase, etc. important Issue identified as high-priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brettcannon @DonJayamanne @d3r3kk