Overview
Using this plug-in JMeter provides an easy way record and replay Appian processes.
JMeter for Appian accomplishes this by hooking into JMeter's Test Script Recorder mechanism. It alters the behavior of most HTTP requests so that additional logic runs when the test is recorded. This logic extracts the standard dynamic values that are passed back and forth when a user interacts with Appian.
Key Features & Functionality
This JMeter plug-in will add post processing to Appian requests/responses to:
The plug-in does not attempt to parameterize end user entered data. This could however be added to the generated test script.
Hi,
In the execution of user load / capacity testing, the JMeter results file is recording 500 errors (such as 502 Bad Gateway and 504 Gateway Time-out); however the Appian environment is not displaying any errors, either in monitoring or the system logs.
Has anyone else experienced this issue? Is there a reason JMeter would record a 500 that does not correspond to any error on Appian-side?
Thank you!
had similar problem with post requests 500 status. and in addition this error {"error":"APNX-1-4198-019","message":"Expression evaluation error [evaluation ID = a431a:aa1ee]: An error occurred while executing a save: This page has timed out. Changes you made may not be saved. Click OK to refresh the page.","title":"An Error Has Occurred"}
Does anyone know how it can be solved?
jsonextractor used
A bit late but... check the "context"'s variable JSONPATH on the previous request. It seems it was changed in later versions. The plugin tries to find the context data with $.context.#v . However, the response context value is under: $.context.value. Check on your failing request if the context looks like
"context":{"type":"stateful","value":"${CONTEXT}","#t":"Map"}
If not, please change and try again.