TL;DR: TaloTrace is an AI-powered QA testing platform that can run your test scenarios automatically every morning, or weekly, at a wall-clock time set in your own timezone, using the latest build you shipped, so findings are waiting before your team logs on. Schedules are set per project and draw on your plan's credits like any other run.
Key Takeaways
Timezone-aware scheduling: Pick a daily or weekly wall-clock time per project, no free-form cron required.
Fresh build every run: A scheduled run tests the latest finalised build, not one pinned when you set up the schedule.
Same credit rules apply: Scheduled runs pass the same credit check as a run you start manually.
Independent review before you see it: TaloTrace verifies each finding before it reaches your inbox.
Evidence with every finding: Each finding includes a recording and the time window where the defect shows.
You're notified when it's ready: In-app and email alerts fire when run results are published.
Why Run Tests Before Your Team Logs On?
Running tests before your team logs on means bugs are already found and verified by the time anyone opens a laptop. Many teams running daily QA passes still start the day by kicking off a test run by hand, then waiting on results. That first hour before anyone touches a keyboard is a cheap time to find a bug, cheaper than waiting until your team or your users hit it mid-workday, but only if the results are already sitting there when the team logs on.
TaloTrace can run your scenarios on a recurring schedule, daily or weekly, at a wall-clock time you set in your own timezone. You do not have to remember to start it, and you do not have to be awake when it runs.
How Do You Set Up a Recurring Test Schedule?
A schedule is configured per project and can optionally be tied to a specific Test Plan. You choose daily or weekly, and a time of day in your timezone; there is no free-form cron expression to write.
A scheduled run is not pinned to whatever build existed when you set the schedule up. Each run tests the latest finalised build, so a morning schedule keeps testing whatever your team shipped most recently rather than an old snapshot.
Scheduled runs pass the same credit check as a run you start yourself from the app or the API. You can still run tests manually whenever you need to scheduling doesn't replace that option. See how TaloTrace builds and runs tests for the full picture of what happens once a run starts.
What Does TaloTrace Actually Test While You Sleep?
Before scheduling anything, you point TaloTrace at your app and, optionally, describe the flow you care about most in plain language, something like "complete a checkout". TaloTrace explores the running app, plans the journeys worth testing, drives each one to a verifiable outcome, and turns completed journeys into replayable scenarios. There are no test scripts to write, though scenarios can also be authored from a chat description or written by hand.
Navigation is sight-based: TaloTrace looks at the screen rather than relying on brittle element IDs, so a scheduled run keeps working after a UI change instead of failing on a selector that moved overnight. Its interaction range covers taps, typing, scrolling, swiping, long-press, double-tap, drag and pinch.
Each run executes automatically on whichever platform matches your app: a cloud-hosted browser, an Android emulator, or an Apple iOS Simulator. For the full breakdown of what each plane covers and where the device matrix applies, see how TaloTrace tests web, iOS, and Android from one platform.
For apps behind a sign-in, TaloTrace uses the test accounts you have stored, including different roles like admin or viewer, so a morning run for an admin flow and a viewer flow can both happen unattended. Read more about autonomous mobile app testing if mobile coverage is what you are scheduling first.
What You Get Each Morning?
Each finding is backed by a screen recording, TaloTrace's reasoning, and step-by-step reproduction, so you are not starting your investigation from a one-line description. The recording carries a marked time window showing exactly where the defect appears, and severity follows a five-level scale, shown with its underlying code.
Code | Severity | Meaning | Examples |
|---|---|---|---|
P0 | Critical | System unavailable | App cannot launch, payments unavailable, complete outage |
P1 | High | Core journey impossible | Cannot checkout, register, or subscribe |
P2 | Medium | Feature works incorrectly | Wrong search results, broken validation, incorrect state changes |
P3 | Low | Experience degraded | Broken layouts, overlapping components, missing labels |
P4 | Trivial | Cosmetic or polish issue | Cosmetic issues and visual inconsistencies |
P0–P4 is TaloTrace's default scale — see the full severity breakdown for how findings map to it. If your team has its own triage guidance, TaloTrace can rate findings against it rather than a generic default.
Results start hidden until a reviewer approves them, the same review pipeline every TaloTrace run goes through. See how TaloTrace verifies findings before they reach you for the full mechanism. For a scheduled morning run specifically, that means:
Low-confidence findings are held back from bulk approval, so a scheduled run doesn't flood the team with unverified noise.
Repeated observations of the same defect collapse into a single issue.
If a scheduled run turns up something already tracked, it's routed to the existing issue instead of opening a duplicate.
You will know the run has finished without checking manually: notifications land in-app and by email once results are published, and again if something is waiting on a reviewer.
What Makes a Scheduled Run Worth Trusting?
The same independent-review pipeline covered above is what makes an unattended morning run safe to rely on, you're not waking up to raw, unverified output. See why TaloTrace separates finding a bug from reporting it if you want the full reasoning behind that design.
Every run's cost is tracked and visible, so a schedule you leave running unattended does not become a line item you cannot explain.
Limits Worth Knowing Before You Rely on a Schedule?
There is no free-form cron. Schedules are daily or weekly presets at a wall-clock time, which covers "every morning" well but will not express something like "every third weekday".
The device matrix is plan-gated. On the free trial, a scheduled run tests the default profile for your platform only; extra device and OS profiles are unlocked on paid tiers. All three execution planes are cloud-hosted and virtual, a browser, an Android emulator and an iOS Simulator, so physical devices are not part of a scheduled run.
If you were hoping to trigger a run from a pull request instead of a clock, that is not available yet; the two ways to start a run today are on demand and on a recurring schedule. Keep an eye on our updates page if that changes.
For apps with an emailed or texted sign-up code, TaloTrace can use a throwaway inbox or number to get past the gate automatically. Treat this as a best-effort convenience for onboarding, not a guarantee for every app.
How to Get Started with Scheduled Testing?
Scheduling lives on the same project as everything else: your Test Plans, stored test accounts and imported docs. Most tiers are published and buyable directly on the pricing page, with custom terms available at enterprise scale.
The fastest way to see a morning schedule set up against your own app is to apply for early access — beta is open now.
Frequently Asked Questions
Can I schedule tests to run every morning in my own timezone?
Yes. Schedules are set per project as daily or weekly presets at a wall-clock time in your timezone, so "every morning" means the time you actually choose, not a server default.
Does a scheduled run test an old build or my newest one?
A scheduled run is not pinned to a build. It tests the latest finalised build each time, so a morning schedule keeps testing whatever your team shipped most recently.
Can I trigger a run from a pull request instead of a schedule?
Not yet. Pull-request-triggered runs are not available today; the two ways to start a run are on demand, from the app or API, and on a recurring schedule.
Do scheduled runs use my plan's credits the same way manual runs do?
Yes. Every scheduled run passes the same credit check as a run you start yourself, so it draws on your plan exactly as a manual run would.
Will I know when a scheduled run has finished?
Yes. You get an in-app notification and an email once results are published, and another if something is waiting on a reviewer.
Can a schedule cover more than one device or browser configuration?
It can, on paid tiers. The device matrix runs the same scenarios across several device or OS configurations in one submission; the free trial runs the default profile for your platform.
