Disruption events

You can incorporate chaos testing into a load test by adding disruption events.

In this topic:

Prerequisites

To add disruption events, you must first configure your Gremlin account in OpenText Core Performance Engineering.

To configure your Gremlin account, select Tools and integrations > Disruption events and enter your Gremlin Team ID and API key.

After configuring your Gremlin account, add disruption events when configuring a load test. For details, see Configure disruption events.

Disruption events data is displayed in the Dashboard. For details, see Dashboard metrics.

Configure disruption events

Before adding disruption events, make sure that you set up your Gremlin account as described in Configure disruption events.

To add disruption events:

1. In the Load tests tab, select a test and click Disruption events in the sidebar. Disruption events already assigned to the load test are displayed. Delete an event, or use the Active switch to make an event active or inactive.

2. To add new disruption events to the load test, click Add to open the Add events dialog box. All available disruption events are listed. Filter the list by attack type or search for a specific event.

3. Select the events to add and click Add. The selected events are added to the load test and displayed in the Disruption events pane.

4. In the Disruption events pane, set the start time for each disruption event. This is the time during the test run that the event should start.

   Note:  

   • Disruption events must end before the load test run completes. A disruption event's start time and its duration cannot exceed the total load test run time.

   • The same disruption event cannot run concurrently in a load test. A disruption event must end before another instance of the same event can be started.

Disruption event data is displayed in the Dashboard. For details, see Dashboard metrics.