[GPCAPIM-348]-[Create load testing framework]-[RP}#166
Merged
BJSS-russell-pollock merged 1 commit intomainfrom Apr 17, 2026
Merged
[GPCAPIM-348]-[Create load testing framework]-[RP}#166BJSS-russell-pollock merged 1 commit intomainfrom
BJSS-russell-pollock merged 1 commit intomainfrom
Conversation
BJSS-russell-pollock
force-pushed
the
feature/GPCAPIM-348
branch
2 times, most recently
from
1c39451 to
69979ae
Compare
BJSS-russell-pollock
force-pushed
the
feature/GPCAPIM-348
branch
26 times, most recently
from
cf894da to
e2774c9
Compare
BJSS-russell-pollock
force-pushed
the
feature/GPCAPIM-348
branch
from
7671d23 to
326c469
Compare
DWolfsNHS
reviewed
Apr 17, 2026
| - Verify that the real API implementation satisfies the consumer's expectations | ||
| - **Key point:** This is where the real API gets tested | ||
|
|
||
| ### Load Testing with Locust ('load/') |
Collaborator
There was a problem hiding this comment.
This section looks to be mid-way through the Contract Testing section, does it need to be moved a few lines down?
DWolfsNHS
reviewed
Apr 17, 2026
| - Tests can be ran in the terminal (headless) or controlled via a web UI. | ||
|
|
||
| **Running Load Tests:** | ||
|
|
Collaborator
There was a problem hiding this comment.
I think its worth noting that the app needs to be running (i.e. make deploy) first.
DWolfsNHS
reviewed
Apr 17, 2026
| make test-load-initial | ||
| ``` | ||
|
|
||
| To run the test using the interactive web UI: |
Collaborator
There was a problem hiding this comment.
Add a note that this requires proxygen set up?
BJSS-russell-pollock
force-pushed
the
feature/GPCAPIM-348
branch
from
326c469 to
2873cd0
Compare
|
|
Deployment Complete
|
DWolfsNHS
approved these changes
Apr 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This ticket is to start working on those performance tests, but with a focus on the tests themselves and not the environment they're running against. This means that we can start the work as early as possible, and use the results to compare against different implementations. For example, this could be very useful when comparing different python frameworks to see how performance differs (even if the raw value from any test isn't useful). It also de-risks the future work, since we'll have load tests we can run at any time.
Context
As part of the beta project work, we are going to need to run performance tests so that we understand how performant the system is under load. This will require a representative environment, with representative delays on downstream calls (if we cannot call the real things).
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.