A Time-Based Test Execution Planner

TestShell Scheduler is a local or networked test execution time planner for optimized execution and station utilization. Scheduler's "Outlook-like" interface allows easy test station allocation and timetabling for each particular test, including setting test priorities and assigning test plans automatically to single or multiple stations.

TestShell Scheduler is an optional module for TestShell Personal and Team Editions and is available as a standalone or a client-server application.

Highlights
Features & Benefits

Highlights

• Automatic scheduling according to time, station and priority
• Test scheduling across single or multiple stations
• Advanced "Outlook-like" interface
• Virtual station locking
• Fully customizable execution rules
• Automatic real-time execution conflict handling
  

 

Top

Features & Benefits 

Optimize the test execution process

• Automatic test scheduling according to:
• Execution duration
• A specific test station (based on availability, location or test requirements)
• Test priority
• Automatic test re-allocation in case of overlaps, delays, priorities and more, allowing dynamic real-time adaptation, and data loss prevention
• Test execution alerts in case of run failure, interruptions, pending clearance and more

Maximize test station utilization

• Schedule tests across single or multiple stations from a central repository for optimized test station utilization and increased execution process efficiency
• All stations are organized on a filterable list
• Automatic allocation of tests to available relevant stations
• Automatic allocation of tests to available time slots
    

Scheduler Reservation Window

Define and customize scheduling criteria

• Customize default reservation options:
• Automatic station assignment
• Test length
• Availability notifications
• Set priorities according to:
• Users
• Test type
• Station

     and more

• Conflict management during scheduling and run-time including overlap rules, interruptions, failed to run actions, priority conflicts and more) 
  

Defining test run time rules

Top