-
Notifications
You must be signed in to change notification settings - Fork 2
P4: Testing Strategy JMeter
We have tested it for 10 requests to establish that the system is functional.
Our approach to testing is to first test the endpoints using Postman, to test that it's functional and also that we have model data to test the endpoint successfully with. Using the model data as reference, we generate mock data using Mockaroo. We then move on to testing the endpoints using JMeter.
We initially tested the dev deployment before we had our Custos deployment ready. During that time, we tested the deployment on JMeter and encountered errors that are mentioned in the Project Report. Some of the errors included frequent 503 Errors, and the Users page on the GUI being stuck on the loading animation.
Once we had our deployment of Custos on Jetstream, we had to test that the endpoints were functional before we stress-tested it. We tested the endpoints using the test collection on Postman. We then tested with 10 requests per endpoint on JMeter. Finally, once we had tested with 10 requests, we went on to test with 1000 requests to test the breaking point of the system.