🎨 Extend locust tests for testing individual endpoints

[bisgaard-itis]

What do these changes do?

• Extend our load testing framework to allow developers to hit endpoints by specifying a HTTP body and HTTP method in tests/performance/locustfiles/deployment_max_rps_single_endpoint.py

Related issue/s

How to test

Dev-ops

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.82%. Comparing base (dc56a2a) to head (bae2054).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7955      +/-   ##
==========================================
- Coverage   87.85%   87.82%   -0.03%     
==========================================
  Files        1848     1848              
  Lines       71283    71196      -87     
  Branches     1250     1248       -2     
==========================================
- Hits        62625    62529      -96     
- Misses       8296     8307      +11     
+ Partials      362      360       -2     

Flag	Coverage Δ		*Carryforward flag
integrationtests	64.29% <ø> (+0.03%)	⬆️
unittests	86.42% <ø> (-0.04%)	⬇️	Carriedforward from 904b669

*This pull request uses carry forward flags. Click here to find out more.

Components	Coverage Δ
api	76.84% <ø> (ø)
pkg_aws_library	93.92% <ø> (ø)
pkg_celery_library	81.13% <ø> (ø)
pkg_dask_task_models_library	79.62% <ø> (ø)
pkg_models_library	93.27% <ø> (ø)
pkg_notifications_library	85.26% <ø> (ø)
pkg_postgres_database	88.18% <ø> (ø)
pkg_service_integration	69.92% <ø> (ø)
pkg_service_library	71.55% <ø> (+<0.01%)	⬆️
pkg_settings_library	90.90% <ø> (ø)
pkg_simcore_sdk	84.99% <ø> (ø)
agent	96.29% <ø> (ø)
api_server	92.29% <ø> (-0.35%)	⬇️
autoscaling	96.03% <ø> (ø)
catalog	92.29% <ø> (ø)
clusters_keeper	99.13% <ø> (ø)
dask_sidecar	91.79% <ø> (ø)
datcore_adapter	97.94% <ø> (ø)
director	76.73% <ø> (ø)
director_v2	91.11% <ø> (-0.02%)	⬇️
dynamic_scheduler	96.69% <ø> (ø)
dynamic_sidecar	90.09% <ø> (ø)
efs_guardian	89.65% <ø> (ø)
invitations	93.60% <ø> (ø)
payments	92.57% <ø> (ø)
resource_usage_tracker	89.10% <ø> (+0.05%)	⬆️
storage	86.30% <ø> (-0.18%)	⬇️
webclient	∅ <ø> (∅)
webserver	87.63% <ø> (-0.01%)	⬇️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dc56a2a...bae2054. Read the comment docs.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sanderegg]

thanks!

[bisgaard-itis]

@Mergifyio queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

The following conditions don't match anymore:

• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • any of: [🛡 GitHub branch protection]
      • check-neutral = system-tests
      • check-skipped = system-tests
      • check-success = system-tests

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.