LogoLogo
HomeSign UpGithub
  • Home
  • Release Notes
  • Getting Started
    • Create your first Test
    • Create Run Settings
    • Analyze the results
      • Job Summary
      • Logs
      • State
      • Payload
    • Look deeper with Metrics
  • Concepts
    • Workspaces
      • Role Based Access Control (RBAC)
      • Invitation Management
      • GitHub Integration
      • Deletion of Workspaces
      • System Status
    • Understanding Tests
      • Stages Management
        • Init Stage
        • Running Stage(s)
        • Finished State
      • Generating Messages
        • Scripting Environment
        • State Object
      • Response Handler
      • Preview Tests
      • Exporting/Importing Tests
        • Import OpenAPI JSON/YAML
      • Locking/Unlocking a test
    • Stateful Simulation
      • Mapping the IoT device lifecycle
    • Protocol Settings
      • MQTT
      • HTTP
      • Using other protocols
    • Run Settings
      • Network Simulation
      • Execution Strategies
      • Client Distribution
    • Scenarios
    • Glob Storage
    • Metrics
    • Mailbox
    • Licensing and Limits
    • Deployment Models
  • Additional Helpers
    • External Libraries
    • Inbuilt Libraries
    • IoTIFY Helper Functions
      • Job Functions
      • Messaging Functions
      • Glob Functions
      • Metrics Functions
      • Mailbox Functions
      • Data Generation Functions
  • platform integrations
    • AWS IoT Connector
  • Guides
    • Smart City
    • Smart Home
    • Load Testing Kafka
  • IoT Testing
    • Overview
      • Feed offline sensor data from Google Sheets to your IoT platform
    • Functional Testing
      • Basic functional test
      • Geofencing Validation
    • Performance Testing
      • MQTT end to end latency Measurement
    • Security Testing
    • Load Testing
    • Test Automation & CI/CD integration
  • API
    • Simulation API
    • Glob APIs
    • Metrics API
  • Glossary
  • Create Account
  • TEMP
    • Getting Started
      • Beginner
      • Developer
      • Tester
    • Walkthrough
    • Protocol Settings
      • CoAP
      • Raw (TCP/UDP/TLS/DTLS)
      • LWM2M
      • NONE
    • Under the hood
    • Google Sheets API
    • Azure IoT
    • Losant IoT
      • Losant Connector
      • Parking Space Management
      • Waste Management
      • Connected Truck
      • Delivery Van
    • Google Cloud IoT Core
    • IBM Cloud
      • Simple Messaging
      • IBM Bluemix: Monitoring Energy Consumption
    • Dweet.io
    • JMeter and why it fails at IoT
Powered by GitBook
On this page

Was this helpful?

  1. Concepts

Scenarios

PreviousClient DistributionNextGlob Storage

Last updated 2 years ago

Was this helpful?

Introduction

There may be times when you need to orchestrate multiple tests all depending on each other. This can be quite tiresome since you need to keep checking the status of the currently running test and start another test when it reaches the required pass or fail status.

With Scenarios, we make it a lot easier for you to orchestrate such complex workflows so that you don't have to spend considerable time on such issues. You can use the easy-to-use editor to create these custom workflows and you can run it at any time with just one click.

To start using Scenarios, click on the Scenarios options in the sidebar. This will take you to the Scenario selector, where all the scenarios that you have created will be listed. To create a new scenario, Create Scenario button on the top right corner.

This will bring you to the Scenario Editor, which is an easy-to-use interface for creating these workflows. The top of this editor has the name of the scenario and control buttons for saving, running, stopping and resetting the scenarios. Below is the actual working area which is divided into 2 parts.

The left houses all the different types of nodes that are supported by us and the right side is where we can drag these nodes and start connecting them to create the workflows. The editor already has a start and an end node and you can connect as many nodes in between as required.

The 2 nodes that we can use are the Test Nodes and the Delay Nodes. The test nodes are the nodes which actually run the simulations, here we can select the test from a dropdown menu. You can select any test you have in your workspace, then select a timeout for this test run, set the Pass and Fail condition percentages and finally the Run settings you want with the particular test. With the delay node, you can have an additional delay after any test run.

It is a good practice to have a small delay of a few seconds between 2 subsequent test runs.

Once you have laid and configured all the nodes, you can join them according to the pass and fail conditions. Each node has 2 outputs, the green being the output for the pass condition and the red being the output for the fail condition. Once all the nodes are connected, you can start running the Scenario.

The nodes will change their colors according to their status (blue: ongoing; red: failed; green: success) and the results for the individual test runs can be found in the results page.