LoadForge allows you to schedule load tests for regular execution, ensuring continuous monitoring of your system’s performance. This is essential for detecting performance regressions, monitoring API SLAs, and adapting to modern CI/CD deployment cycles where applications change frequently.

Why Schedule Load Tests?

In the past, performance testing was done once a year before a big release. Today, with continuous deployment (CI/CD), applications change daily or even multiple times per day. Scheduling load tests ensures that every new deployment is checked for performance issues.

Tip: LoadForge allows you to compare test runs over time, making it easy to spot regressions and performance degradation.

LoadForge Alerts You to Performance Drops

By scheduling recurring tests, LoadForge will notify you if:

  • API SLAs are violated (e.g., response times exceed defined thresholds).
  • Performance suddenly drops due to a new deployment.
  • Error rates increase, indicating system instability under load.

How to Schedule a Load Test

Scheduling a test in LoadForge is simple:

  1. Navigate to Schedule:

    • In the LoadForge control panel, go to the ‘Tests’ menu and select ‘Schedule’.
  2. Select Your Test:

    • Choose an existing test you want to run on a schedule.
  3. Define Schedule Details:

    • Cron Expression: Specify when and how often the test should run.
    • Once-Off or Recurring: Choose whether this test should run only once or on a set schedule.
    • Run Duration: Define how long the test should execute.

Tip: If cron expressions seem complex, LoadForge provides preset options for common schedules like hourly, daily, and weekly.

Understanding Cron Expressions

LoadForge uses cron expressions to define when tests run. Cron syntax allows you to specify schedules based on minutes, hours, days, months, and weekdays.

Basic Cron Examples

0 */6 * * *    # Run every 6 hours
15 3 * * *     # Run daily at 3:15 AM
0 0 1 * *      # Run at midnight on the first of every month

Advanced Cron Examples

# Execute at 1:15 p.m. and 1:45 p.m. every Tuesday in June
15,45 13 ? 6 Tue

# Run every 5 minutes between 1:00 p.m. and 1:55 p.m.
0/5 13 * * *

For a detailed explanation of cron expressions, refer to this guide.

Best Practices for Scheduling Tests

  • Run smaller tests more frequently (e.g., API response monitoring every hour).
  • Schedule full load tests during off-peak hours to avoid disrupting users.
  • Use weekly or monthly tests to track long-term trends.
  • Set up alerts so you’re notified if performance drops.

By leveraging scheduled load tests, LoadForge helps you stay ahead of performance issues and ensures your system can handle real-world traffic conditions at all times.