Resources are assets that can be accessed and controlled depending on the role of the member. They are also organized into a few levels, but unlike the permission levels, they have to do with the actual test artefacts. You can view resources like folders and sub-folders in a directory.
A flood is a single and specific instance of a load test being executed. You can see a list of floods by clicking on the Floods button on the taskbar. Below the graph, you'll see a list of floods, each of which you can click to go into the Flood view.
Each flood is identified by a unique flood number (the floods in the screenshot above have IDs of #874, #873, #856, and #855, respectively) and a flood UUID. You can find the UUID by clicking into the flood view and then looking at the URL. You'll see something like this:
The UUID will be the string directly following
/flood/. In the example URL above, the flood UUID is
6ZoWAqOdDLetZH5G9dX4fQ. You'll only need the UUID if you're using our API or if you'd like to give support details to troubleshoot a particular flood.
A stream is a collection of floods. While you can create completely different floods from the same stream, the intention is to use streams like test cases or test scenarios.
For example, you might have a stream called "Peak Load Test - 500 users over 30 minutes". Then, every flood in that stream could be one instance of an execution of that same basic test.
To create another flood in the same stream, you can use Start more like this.
A project is a collection of streams. While you can group completely different streams and floods into the same project, the intention is for you to use projects to group similar streams and floods together.
For example, you might have a project for your corporate website, and another one for your e-commerce shop.