Meet TestDino at Dreamforce 2026
AI agents write code faster than your team can verify it. TestDino records every Playwright run from your CI, so every pull request, human or agent, clears the same check before merge.
Meet us off the expo floor
Dreamforce fills three city blocks for three days. Book a working session near Moscone instead of a badge scan.
On the ground September 15-17.
45 to 60 minutes, near Moscone.
Your CI pipeline and Playwright coverage.
Written plan and a trial workspace to keep.
attendees at Dreamforce
sessions in the catalog
on the ground
private working sessions
Where Salesforce testing is heading
Six shifts hitting Salesforce QA teams at once. Bring one to a whiteboard session.
Agent evals
Agentforce Testing Center scores utterances in a sandbox. Your agent's behavior in the live app still needs end-to-end checks.
Judges need ground truth
Judge scores drift without deterministic pass/fail signals underneath. Playwright assertions give you that baseline.
Shadow DOM automation
Selenium-era locators fight Lightning Web Components. Playwright pierces shadow roots natively.
Migration deadline: Dec 31, 2026
A forced migration is a free re-evaluation. Teams are moving to open-source Playwright with a reporting layer on top.
The storefront is a web app
Composable Storefront on PWA Kit runs on SCAPI and OCAPI. Playwright covers the UI and the APIs in one run.
Three releases a year
Winter, Spring, and Summer releases force regression on Salesforce's calendar, not yours. Data Cloud changes ride along.
One gate between code and merge
TestDino sits between your CI and your merge button. Each capability links to how it works.
Three days on the ground
Sessions run 45 to 60 minutes near Moscone. Each day has a default theme, not a fixed one.
Tuesday
Agents and evals
Map your Agentforce test coverage and design the eval layer under it.
Wednesday
Test architecture
Whiteboard your CI pipeline, LWC automation, and a Provar exit plan.
Thursday
Commerce, data, and releases
Storefront coverage, Data Cloud validation, and a three-release regression plan.
What we take in the session
Sessions run 45 to 60 minutes near Moscone. Bring the one that is stuck.
Each release still means days of manual clicking.
Your renewal is on the table before Dec 31, 2026.
A pilot is live with no eval plan behind it.
Coding agents ship faster than you can verify the runs.
Teams love what we built
See why developers choose TestDino to ship faster and debug smarter
We were on the default Playwright reporter, and it was tedious to dig through; half a day gone just triaging failures. The TestDino MCP changed that for us. I now run through the failures in minutes instead of devoting half a day to it, and pulling the latest runs straight through the MCP sped up bug triage drastically. AI failure classification and Slack reports do the rest. It's saved us weeks.
To triage failures, down from half a day
Saved across the team
Migrating to TestDino from our previous tool was an easy decision. The features are stronger, the cost is lower, and the interface makes debugging far less painful. Flaky test detection and AI failure classification have simplified debugging and reduced our CI costs by cutting down reruns and noisy failures.
Reduction in CI costs
Less time triaging failures
Over 30 flaky tests and no structured way to track them, just CI artifacts and morning guesswork. TestDino's "Most Flaky Tests" feature broke this pattern. We can see failure trends now and pull up video recordings of exactly what went wrong. The TestDino MCP server is the magic piece on top, I ask my Claude agent about a failure and it pulls full context from TestDino without switching tabs. We went from 30-something flaky tests down to 3 or 4.
Fewer flaky test reruns
Faster failure triage
Leave with a 30-day plan
Every working session ends with a written 30-day plan and a free trial workspace. Both are yours to keep.
- 1
Week 1
Connect CI and baseline your pass rate and flake map.
- 2
Week 2
Set up trace-based triage and quarantine known flakes.
- 3
Week 3
Wire the MCP server into Claude Code or Cursor.
- 4
Week 4
Review trends and set your release gate.