Maeris logo
Sign In

Schedule Your Regression

Automate your regression testing by scheduling test suites to run at specific times or intervals. This ensures continuous validation of your application without manual intervention.

What is Test Scheduling?

Test scheduling allows you to automatically execute your test suites at predetermined times or intervals. This is essential for regression testing, where you need to regularly verify that existing functionality still works after new changes.

Benefits of Scheduling

  • Continuous Testing: Run tests automatically without manual intervention
  • Early Detection: Catch regressions as soon as they're introduced
  • Consistency: Ensure tests run at the same time every day or week
  • Resource Efficiency: Schedule tests during off-peak hours
  • Team Awareness: Regular test runs keep the team informed about application health

Creating a Schedule

Step 1: Select Tests

Choose which tests to include in your scheduled regression suite.

  • Select individual tests from the Notebook
  • Choose tests by tags (e.g., @regression, @smoke)
  • Select entire test suites or groups

Step 2: Configure Schedule

Set when and how often the tests should run.

  • Choose schedule type (daily, weekly, monthly, custom)
  • Set specific time for execution
  • Select timezone
  • Configure recurrence pattern

Step 3: Configure Execution Settings

Set up how the tests should be executed.

  • Choose execution environment
  • Select browser(s) for execution
  • Configure parallel or sequential execution
  • Set up notifications and alerts

Schedule Types

Daily Schedule

Run tests every day at a specific time. Ideal for critical regression tests that need frequent validation.

Example: Run smoke tests every day at 2:00 AM

Weekly Schedule

Execute tests on specific days of the week. Perfect for comprehensive regression suites that take longer to run.

Example: Run full regression every Sunday at 10:00 PM

Monthly Schedule

Run tests on specific dates each month. Useful for extensive test suites or periodic validation.

Example: Run complete test suite on the 1st of every month

Custom Schedule

Create custom schedules with specific recurrence patterns. Flexible option for unique requirements.

Example: Run tests every 3 days, or on specific weekdays only

Execution Settings

Environment Configuration

  • Select the target environment (dev, staging, production)
  • Configure environment-specific variables
  • Set up authentication for scheduled runs

Browser Selection

  • Choose which browsers to test on
  • Run tests on multiple browsers in parallel
  • Configure browser-specific settings

Execution Mode

  • Sequential: Run tests one after another
  • Parallel: Run multiple tests simultaneously
  • Mixed: Combine both approaches for optimal execution time

Notifications and Alerts

Configure notifications to stay informed about scheduled test executions and results.

Notification Options

  • Email Notifications: Receive results via email
  • Slack/Teams Integration: Get notifications in your team chat
  • Webhooks: Send results to custom endpoints
  • Dashboard Alerts: Visual indicators in the Maeris dashboard

Alert Conditions

  • Notify on test failures
  • Alert when execution time exceeds threshold
  • Notify on schedule execution start/completion
  • Alert when test health score drops

Managing Schedules

Schedule Management

  • View all active schedules in the Schedules section
  • Edit existing schedules to modify timing or test selection
  • Pause schedules temporarily without deleting them
  • Delete schedules that are no longer needed
  • View execution history for each schedule

Monitoring Scheduled Runs

  • Track upcoming scheduled executions
  • Monitor currently running scheduled tests
  • Review past scheduled run results
  • Analyze schedule execution trends

Best Practices

  • Start with Smoke Tests: Schedule critical smoke tests to run frequently

    Quick validation of core functionality

  • Schedule During Off-Peak Hours: Run extensive tests when system load is low

    Reduces impact on application performance

  • Use Tags Effectively: Organize tests with tags for easy scheduling

    Simplifies test selection and management

  • Set Up Notifications: Configure alerts for failures and important events

    Ensures timely response to issues

  • Review Regularly: Periodically review and update schedules

    Keeps schedules aligned with testing needs

  • Balance Frequency: Find the right balance between test frequency and resource usage

    More frequent = earlier detection, but higher resource cost

Next Steps

After setting up your schedules, explore additional features: