Release note·

    Configurable session state lifetime

    Output state validity is no longer hardcoded to six hours.

    When a test produces an output state (cookies, local storage, IndexedDB) that downstream tests depend on, that state used to expire after a hardcoded six hours. For some applications six hours is fine. For others (long-lived sessions, daily test runs, slower QA cadences) it forced unnecessary re-logins.

    Output state validity is now a per-application setting, configurable from 5 minutes up to 7 days under Project Settings → Applications → Edit → Session State Lifetime.

    Ready to end the QA bottleneck?

    See how QA.tech agents test your product in a 30-minute demo – and leave with a plan to reclaim those hours.

    Get a demo