Test Scheduling (Standalone)

How to schedule automated test executions.

Please note

The content on this page pertains only to the Standalone StormForge Performance Testing environment at https://app.stormforger.com.

In this guide you will learn how to schedule your test cases to be executed automatically based on a schedule that you define.

This feature is only available with an active subscription. If you have any questions, feel free to contact us any time!

Automated Test Execution

Automated test execution can be a useful and simple way to run your load tests on a regular basis. You can either do that yourself using our forge CLI combined with your continuous integration tool, or use our simple scheduling feature.

Let’s say you want to schedule your main load test (called blackfriday2018) against your staging environment to run every day during the week from Monday to Thursday at 09:30 UTC.

To do that select your organisation and go to “Scheduled Tests”. By clicking “Create Configuration” you can select a test case to be executed and a cron notation to tell us when you want the test runs to be performed.

To run your test as described before, you can use 30 09 * * 1-4 (Hint: Do you know crontab.guru?) as your cron line:

Create Scheduling Configuration

After you have saved your new scheduling configuration, you can see when we will execute your test the next time, when it was executed the last time and if the test case itself is valid and ready for execution.

List of Scheduling Configurations

We will automatically launch test runs according to your schedule.

Launching Test Run via CLI

As already mentioned you can also trigger test run launches via our command line tool, called forge. You can find an installation guide here. For a full usage description, please see our current CLI documentation.

$ forge test-case launch acme-inc/blackfriday2018

There are various flags available, e.g. to wait and watch the currently executed test run. Try forge test-case launch --help to learn more.

PS: You can nicely combine your triggered test executions with our automated non-functional requirements check feature.

Last modified August 3, 2022