At Flood, we believe you should be able to run your load tests from anywhere, so we provide a few different options for using Flood to scale up your testing.
First, you'll need to decide whether you need to run your tests from the cloud or from your on-premise infrastructure. Then, follow the links below to find out more options.
As long as you have a subscription with Flood, you'll be able to make use of any or all of these options.
Nicole explains the different options for running floods
On the cloud
Load testing on the cloud means that we will be starting virtual machines for you to run your scripts from using one of our cloud providers, either AWS or Azure.
Option 1: Demand infrastructure
This is the easiest way to get started, because they require the least set up from your end. Floods on team plans are executed from our own AWS account, but all of that happens in the background. All you'll need to do is run floods from the Flood UI and we'll take care of the rest.
This is a step up in complexity from Option 1. Option 2 allows you to run floods using your own cloud accounts, whether that's with AWS or Azure. You'll need to integrate Flood with AWS or Azure and allow Flood to start virtual machines on those accounts on your behalf.
To generate load using infrastructure you already have on-premise or in a data center, you can use Flood Agent. Flood Agent allows Flood to start load tests using machines that you specify.
Good question! We've gone through this in more detail in this article.
I don't know which one to choose!
Here's a summary to help you decide.
If you want the least amount of set up: Option 1 - Cloud: Demand
If you already have an AWS/ Azure account: Option 2 - Cloud: Host Your Own
If your company already has load generators or a data centre: Option 3 - On-Premise