SoapUI hangs with values of attributes that are too long.
in a soap or rest request, try to assign a 30,000 or more character string (30KB) to any attribute/parameter (like currency in currency converter)
Then you will see how it get too slow and even hangs out when you want to toggle between request and response panes or select the request/response bodies.
I know that no one would send such requests normally, but this is a typical test that we call it "Flood test" or "buffer overflow test" to find the server's behavior in both error handling and security aspects.
If SoapUI can not handle this amount of data, it should restrict user to not put more than x chars. You'll figure how useful it would be when you work on a script for two hours and then loose all that work because SoapUI doesn't respond and you have to kill it!
Then you will see how it get too slow and even hangs out when you want to toggle between request and response panes or select the request/response bodies.
I know that no one would send such requests normally, but this is a typical test that we call it "Flood test" or "buffer overflow test" to find the server's behavior in both error handling and security aspects.
If SoapUI can not handle this amount of data, it should restrict user to not put more than x chars. You'll figure how useful it would be when you work on a script for two hours and then loose all that work because SoapUI doesn't respond and you have to kill it!
