Understanding and troubleshooting test results

Interpreting results correctly is essential for identifying bottlenecks, optimising performance, and ensuring a smooth user experience.

Points to remember

1. Use "View Results in Tree" to see detailed error and API responses in Sample result column JMeter GUI.
2. Use "Summary Report" to get summarised results of all API call and error
3. If a test-case logic consists of 'x' API's ,total number of API calls will be 'x' times number of users (x*users).
4. Error in Initial API will result in Error in Next API.
5. A GET API may be redirected and can considered as pass (due to 200 response from Faveo) even if previous API is failed ,such result is should be considered as failed case and summary is evaluated considering such cases.
6. If the number of API call exceeds "x*users", try to troubleshoot the script for 1 user and retry the test run.
7. Redirected APIs will have 2 or more sub-API calls, Can be verified in "View Results in Tree" Listener.
8. Repeat a test at least 4 times to get better understanding and accuracy of test results.

Troubleshooting the test cases

1. Run the script once from the JMeter GUI , to get better understanding and troubleshoot as per the error in the JMeter log.
2. Even on Correct test script and credentials , instance might give "token expired" response . Check with the developers and ask about "CsrfToken".
3. Sometimes due to null values in the mandatory fields , Predefined Condition failed is received . Check the variables/parameters used to send data in the HTTP request.
4. In case duplicate results are visible in the listeners . Kindly toggle/disable the listeners in the script. Jtl files result can be seen even if listeners are disabled.