Self-Managed Execution
Test suites shouldn't require constant babysitting. Failed tests shouldn't sit in queues waiting for you to manually debug the failure and restart them. Time travel scenarios shouldn't depend on someone remembering to change clocks to the right date, in the right order.
CenterTest Self-Managed Execution monitors test results and automatically retries failed scenarios, resumes suspended tests from their Restart Points, restarts suspended message queues, and coordinates clock changes for time travel workflows - all without manual intervention.
Self-Managed Execution provides autonomous test orchestration that monitors execution results and takes appropriate action based on scenario state and configured parameters.
When scenarios fail, Self-Managed Execution can either rerun the test, or restart the test from the last successfully complete step in the workflow.
Restart patterns are configurable:
Maximum retry attempts before marking as failed
Delay between retry attempts
Conditions that qualify for retry versus immediate failure
CenterTest prevents false failures by restarting tests that are waiting for document generation, paused for clock changes, or interrupted due to environment unavailability. Self-Managed Execution monitors these suspended scenarios and resumes them from the point of failure.
For example, when a test fails after creating an account and policy but before filing a claim, Self-Managed Execution restarts the tests from the claim creation checkpoint.
Previously created data (account number, policy number) is preserved and reused. This dramatically reduces test execution time and prevents orphaned test data accumulation.
Time travel orchestration coordinates date-dependent scenario execution across the entire test suite. When time travel scenarios suspend at Restart Points waiting for specific conditions, Self-Managed Execution:
Tracks suspended scenarios: Monitors which scenarios are waiting for which specific conditions such as clock changes or document production
Coordinates with Best Day calculation: Identifies the optimal next clock change that allows the maximum number of suspended scenarios to resume simultaneously
Executes automatic clock changes: Changes and synchronizes system clocks across PolicyCenter, BillingCenter, and ClaimCenter when configured for automated clock management
Triggers automatic resumption: When the system clock reaches required dates, eligible scenarios resume without manual intervention
Self-Managed Execution handles the unpredictable realities of enterprise testing: slow document generation, erratic queue processing, temporary endpoint failures, and time travel dependencies. Rather than failing immediately, it retries within your configured constraints—allowing large test suites to run hands-off. Every restart is logged with its cause, giving DevOps teams visibility into failure patterns and the data needed to identify root causes and systemic issues.
This automation enables large time travel test suites to execute with minimal human intervention. Teams define date conditions in their scenarios, and CenterTest handles the orchestration of suspension, clock coordination, and resumption across the entire suite.
Self-Managed Execution can be turned on when manually executing a test suite, or it can be triggered via CI/CD pipeline parameterization. No additional infrastructure, specialized agents, or external orchestration tools are required beyond the normal test execution environment.
Learn more by exploring our FAQ below, or schedule a consultation to talk to one of Kimputing's test automation specialists.