Restart Points

Restart Points are checkpoints within scenarios that enable CenterTest to suspend a test from specific, completed steps, rather than starting over from the beginning. They're like pit stops for your tests - keeping things moving without taking you off the track.

Let’s say you have a test that creates a policy, then submits a claim. If the scenario fails because of a login issue with ClaimCenter, the test simply restarts – skipping the account and policy creation (using previously created data) and picking up directly at claim creation.

You can define any number of restart points that make logical sense for your scenario to avoid starting tests over from the beginning. Restart points ensure you are catching real defects by eliminating false failures related to time travel conditions, document generation, or environmental hiccups.

Network timeouts, temporary screen delays, environment unavailability - issues that would normally fail a test - instead trigger a restart from the last successful step in your scenario.

Test data is preserved to maintain environment cleanliness. Without Restart Points, failed tests leave behind orphaned accounts, policies, and claims that clutter test environments. Suspended scenarios resume and complete using the data that was already created, preventing accumulation of abandoned test artifacts.

Multiple checkpoints within a single test enable a comprehensive, end-to-end scenario to execute intelligently. Define restart points after account creation, policy binding, claim filing, or payment processing. Regardless of where failure occurs, the test resumes from the last successfully completed step.

CenterTest Restart Points are foundational to Time Travel testing, document validation, and comprehensive end-to-end policy lifecycle scenarios.

Learn more by exploring our FAQ below, or schedule a consultation to talk to one of Kimputing's test automation specialists.