Drop MQTT Connection Test Step

About Drop MQTT Connection test step

Use this test step to simulate a planned or unexpected disconnection from the MQTT broker to test scenarios in which dropped connections are a factor.

Editing Drop MQTT Connection test step

You can modify test step settings in its editor:

MQTT Testing: Simulating connection breaks

Connection to MQTT server

Settings

Configure connection dialog

Use the Configure Connection dialog to configure connections used by the test step. You use the same dialog to create a new connection or to update the connection from a legacy version.

MQTT Testing in ReadyAPI: Configure connection dialog

Important

The connection may be used in any test case in the project, so only project-level property expansions will work correctly for connection settings.

MQTT Testing in ReadyAPI: SSL Properties

Enable the check box if the MQTT server requires authentication.

MQTT Testing in ReadyAPI: SSL Properties

If you enable storing Will messages on the MQTT server, this message will be sent to listeners if the "publisher" client disconnects from the server without sending the Disconnect message.

MQTT Testing in ReadyAPI: SSL Properties

Note

You can connect by specifying the CA certificate without filling in the other parameters.

Property list

Besides the test step editor, you can adjust the test step’s behavior by using its properties in the Properties and Custom Drop MQTT Connection Test Step Properties panels in the Navigator.

Properties

Name

Description

Name

The test step’s name.

Description

Text describing the test step.

Custom Drop MQTT Connection Test Step Properties

Values on the Custom Drop MQTT Connection Test Step Properties tab are available to other test steps in your project. For instance, you can verify these property values with the Assertion test step, check them, and change the execution flow with the Conditional GoTo test step.

You can load values of custom properties from a file or save them to a file. To learn more, see About Properties.

This tab contains the following properties that provide access to the request and response data:

Name

Description

CertCAPEM

Specifies the fully qualified path to the certificate authority (CA) certificate that was used to sign the server certificate.

Note

Corresponds to the CA certificate option specified on the SSL Settings tab of the connection settings.

ServerURI

Specifies the MQTT server’s URL with the used protocols.

Note

Corresponds to the ServerURL option specified on the General tab of the connection settings.

CertKeyPEM

Specifies the fully qualified path to the client key file.

Note

Corresponds to the Key file option specified on the SSL Settings tab of the connection settings.

ClientID

The client identifier is used by the server to identify a client.

Note

Corresponds to the ClientID option specified on the General page of the connection settings.

CertClientPEM

Specifies the fully qualified path to the client’s certificate that will be used to sign messages.

Note

Corresponds to the CA certificate option specified on the SSL Settings tab of the connection settings.

CertSniServer

Specifies the host name of the server, to which you want to connect.

Note

Corresponds to the Server host name option specified on the SSL Settings tab of the connection settings.

Login

The username for connecting to the MQTT server.

Note

Corresponds to the Login option specified on the Authentication page of the connection settings.

CertKeyPassword

Specifies the password for the client’s private key file.

Note

Corresponds to the Key password option specified on the SSL Settings tab of the connection settings.

Password

The user password for connecting to the MQTT server.

Note

Corresponds to the Password option specified on the Authentication page of the connection settings.

Logging

If the test step is run as part of a test case, you can see the test log in the Transaction Log panel.

See Also

Publication date: