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

[Test] Estimate time of java project build and run inside Che Code Editor in performance tests #22127

Merged
merged 5 commits into from
Apr 5, 2023

Conversation

SkorikSergey
Copy link
Contributor

@SkorikSergey SkorikSergey commented Apr 4, 2023

What does this PR do?

This PR adds api load tests scripts that will be used in DevSpaces performance testing.

What issues does this PR fix or reference?

Openshift DevSpaces issue - Estimate time of java project build and run inside Che Code Editor in performance tests.

How to test this PR?

  1. Create test users on cluster using performance-users job.
  2. Api load test starts by command like:
./api-load-tests.sh -u user  -p load-user -s lombok -n 11 -c 1 -b https://devspaces.crw-qe.com -o https://api.ocp410.com:6443
    -u base username 
    -p common password 
    -b URL of DevSpaces 
    -o Openshift cluster URL
    -s test suite (by default its php)
    -n number of users ${NC} usernames will be set in format <username>1, <username>2(by default its 1) 
    -c count on how many times one user should run a workspace(by default its 1)

For now php, cpp, python, lombok and quarkus suites are available for testing.

  1. Tests results adds to result.txt with format like:
Load testing for 11 users x 1 workspaces took 215 seconds
11 tests passed
0 tests failed
Workspace startup time: 
min: 37 second
avr: 44 second
max: 50 second
Project build time:
min: 140 second
avr: 142 second
max: 146 second

All logs from test pods saved in reports folder.

PR Checklist

As the author of this Pull Request I made sure that:

Reviewers

Reviewers, please comment how you tested the PR when approving it.

@SkorikSergey SkorikSergey added status/in-progress This issue has been taken by an engineer and is under active development. area/qe labels Apr 4, 2023
@SkorikSergey SkorikSergey self-assigned this Apr 4, 2023
@che-bot che-bot added the target/branch Indicates that a PR will be merged into a branch other than master. label Apr 4, 2023
@SkorikSergey SkorikSergey marked this pull request as ready for review April 5, 2023 09:26
@SkorikSergey SkorikSergey added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Apr 5, 2023
@SkorikSergey SkorikSergey merged commit bb0dffc into main Apr 5, 2023
@SkorikSergey SkorikSergey deleted the apiLoadTests branch April 5, 2023 09:58
@che-bot che-bot removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/qe target/branch Indicates that a PR will be merged into a branch other than master.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants