Una prueba de carga SOAP le permite probar el rendimiento de un servicio web basado en SOAP bajo carga de usuario.
Configuración de una prueba
Puede configurar manualmente una solicitud SOAP mediante un sobre SOAP o puede utilizar el Asistente SOAP haciendo clic en el botón Usar WSDL en la parte superior de la página.
El asistente HTTP/SOAP le permite especificar una dirección URL WSDL y le permite seleccionar parámetros válidos para probar antes de continuar.
Introduzca la URL de la página en la que desea realizar la prueba. Especifique toda la dirección URL, incluido HTTP. Por ejemplo, “http://www.example.com/wsdl.asmx?WSDL.”
Umbral de validación de tiempo (en segundos)
Enter the number of seconds the system should wait for a response from the target resource before returning an error. If this is left blank the default timeout is 120 seconds.
El campo de encabezado de solicitud HTTP SOAPAction se puede utilizar para indicar la intención de la solicitud HTTP SOAP. El valor es un URI que identifica la intención. SOAP no impone restricciones en el formato o especificidad del URI o que se puede resolver. Un cliente HTTP DEBE utilizar este campo de encabezado al emitir una solicitud HTTP SOAP.
Los servidores, como los firewalls, pueden utilizar la presencia y el contenido del campo de encabezado SOAPAction para filtrar adecuadamente los mensajes de solicitud SOAP en HTTP. El valor del campo de encabezado de cadena vacía (“”) significa que el URI de solicitud HTTP proporciona la intención del mensaje SOAP. Ningún valor significa que no hay ninguna indicación de la intención del mensaje.
Escriba el cuerpo de la solicitud XML.
Content Validation Keywords are used to ensure that the expected content was loaded onto a web page. In the Keyword fields, you can specify one or more words or phrases that you wish to search for in the web page content. If the expected keywords are not found, the task will return an error.
You can enter multiple strings into the keyword fields. The values you enter can be separated by logical expressions as follows:
{[("keyword1"&"keyword2")|!"keyword3"]}
Where:
{[ – keyword expression start;
]} – keyword expression end;
() – grouping brackets;
& – logical AND;
| – logical OR;
! – logical NOT;
“string” – a keyword.
A successful keyword expression must include the start and end brackets as follows:
{["keyword"]}
The HTTP authentication protocol is used to allow users to access content on some websites.
The following authentication schemes are available:
- Basic Authentication: This method encodes the username and password in base64 and sends them in the request header. It’s simple but not secure unless used with HTTPS.
- Digest Authentication: This scheme hashes credentials using a nonce (a random value) before sending them over the network, providing better security than Basic Authentication by preventing replay attacks.
- NTLM Authentication: A challenge-response mechanism developed by Microsoft, NTLM is used for securing credentials in Windows environments. It provides strong security by using multiple hashing and challenge-response protocols.
Once provided, login credentials will be passed along with the request header to the web server.
- Username: contains a username for HTTP/S authentication.
- User Password: contains a password for HTTP/S authentication.
Do not confuse HTTP authentication with other authentication schemes such as Bearer Authentication that involves bearer tokens and OAuth 2.0 that uses access tokens.
Read the articles on Basic Authentication Username and Password and Monitoring OAuth 2.0-based APIs for more information.
The default User-Agent header is set to:
User-Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0; .NET CLR 1.1.4322; .NET CLR 1.0.3705; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) DMBrowser/2.1 (SV)
However, the user-agent string can be replaced with any other string. To do this, add a custom header with the name “user-agent” and the specific value needed.
The DNS Options feature allows users to choose how domain name server (DNS) requests are conducted during a test.
The Custom DNS Hosts section allows setting up the mapping of IP addresses to hostnames. IPv6 and IPv4 DNS resolutions are supported.
To specify the mapping, enter the IP address and the hostname in the corresponding fields.
Examples:
192.168.107.246 example.com user.example.com userauth.example.com tools.example.com
192.168.107.246 example.com
192.168.107.246 user.example.com
192.168.107.246 userauth.example.com
See also: DNS Mode Options.
Tenga en cuenta que la opción no es compatible con los agentes in situ de LoadView. Para obtener instrucciones detalladas sobre cómo configurar hosts DNS personalizados para el agente in situ, visite el artículo Cómo configurar hosts DNS personalizados para pruebas de carga con el agente in situ de nuestra base de conocimientos.
If you want to ignore an error with a specific code and type while testing, you can configure the Ignore Error Codes option in the test target settings. If the system detects a response with the specified error type and code, the response will be considered as successful and its status will be changed to OK. Note that ignored errors will not be reflected on the reports and can’t be tracked down.
You can find a comprehensive list of Error Codes in the HTTP Status Codes List | HTTP Error Codes Explained article of this wiki.