Skip to content

Run fault Scenarios

In this guide, you will learn how to run fault scenarios and read the generated report.

Prerequisites

  • Install fault

    If you haven’t installed fault yet, follow the installation instructions.

  • Generate Scenario Files

    If you haven’t created a scenario file, please read this guide.

Run a Scenario File

We will explore now how to run scenarios generated to verify the resilience of the fault demo application itself.

  • Start demo application provided by fault

    fault demo run  # (1)!
    1. The application under test must be started for the scenario to be meaningful. Otherwise, the scenarios will all fail.

  • Run a scenario file

    fault scenario run --scenario scenario.yaml

Run Many Scenario Files

We will explore now how to run scenarios generated to verify the resilience of the fault demo application itself. In this specific use case, we assume you want to run many scenario files at once and that they are located in the same directory.

  • Start demo application provided by fault

    fault demo run  # (1)!
    1. The application under test must be started for the scenario to be meaningful. Otherwise, the scenarios will all fail.

  • Run scenario files located in a directory

    fault scenario run --scenario scenarios/  # (1)!
    1. fault will load all YAML files in that directory.

Run a Scenario on Kubernetes

The default behavior is to execute a scenario locally to where the command is started. A scenario offers a way to run the proxy from within a Kubernetes cluster.

  • Configure the scenario to run on a Kubernetes cluster

    context:
  runs_on:
    platform: kubernetes
    ns: default  # (1)!
    service: nginx  # (2)!
    1. The namespace of the target service
    2. The target service which should be part of the test chain

    The scenario will be executed locally but the proxy will be deployed inside the cluster directly.

Next Steps