Skip to content

Product updates

What shipped, and why it matters.

New capabilities in TaloTrace, written for the people who use them: the problem, what changed, where to find it, and what it changes for your team.
  1. Update 06OnboardingIntegrationsIn development

    Product knowledge and test accounts: your documents and logins ground every run

    Bring in the knowledge your team already wrote, and let TaloTrace sign in for itself on every run.

    Read the update

  2. Update 05PlatformIn development

    Automatic test creation: TaloTrace explores your app and writes the scenarios

    The suite exists before anyone has scheduled the work to write it.

    Read the update

  3. Update 04PlatformIn development

    Self-healing tests: a redesign no longer breaks your test suite

    The maintenance bill is why most teams give up on automation. This is the part that goes away.

    Read the update

  4. Update 03PlatformIn development

    Independent bug review: nothing reaches your backlog until the evidence backs it

    The cost of an untrustworthy bug report isn't the bug. It's the hour spent discovering there was never a bug.

    Read the update

  5. Update 02PlatformIn development

    Evidence and replay: every finding opens on the clip that proves it

    Engineers stop paying the reproduction tax on every report, because the proof is already attached.

    Read the update

  6. Update 01PlatformIntegrationsIn development

    Scheduled runs and tracker export: testing runs itself, findings reach your board

    Testing no longer waits on somebody remembering to ask for it, and what it finds lands where your team works.

    Read the update

What's coming

Next on the list.

What the team is building now, from migrating your existing scripts to verified fixes.

  • In development

    Migrate existing scripts

    Convert Playwright, Cypress, Appium and Maestro scripts into TaloTrace scenarios, keeping their intent and assertions.

  • In development

    MCP server access

    A scoped credential so your own AI tools or CI can trigger runs and fetch results.

  • In development

    API testing

    API evidence that helps diagnose and validate user-facing failures.

  • In development

    Root-cause analysis

    Investigate the events leading to a failure and narrow down where and why it happened.

  • In development

    Findings mapped to code

    Associate a finding with the components and code paths most likely involved.

  • In development

    Verified fixes

    Test each candidate fix in an isolated environment, never merged into production, re-running the failing and affected journeys before anyone trusts it.

See what TaloTrace finds.

Give Nico your application. Get back the journeys, the failures, and the evidence.

Test your applicationBook a demo