Post

Joan León
@nucliweb.net

One thing I’m experimenting with for a performance audit: Using RUM data + @debugbear.com MCP to build synthetic tests based on how the product is actually used RUM → real user behaviour → MCP → representative synthetic tests www.debugbear.com/docs/mcp #WebPerf #RUM #MCP

debugbear.comAccess Web Performance Data With The DebugBear MCP Server | DebugBearConnect AI assistants like Claude and ChatGPT to DebugBear using the Model Context Protocol (MCP) to run tests, query metrics, and manage projects.
PingRoom
@pingroom.bsky.social

RUM to synthetic feels useful because it keeps coverage tied to real user paths. How are you choosing which outlier sessions become tests without turning a one-off incident into a brittle suite?

Joan León
@nucliweb.net

I don’t turn single outliers into tests. Tests come from segments with volume: p75 device, connection and the top paths by traffic. Outliers go to investigation first; if the pattern repeats across sessions, then it earns a test.

0 reposts0 likes

PingRoom
@pingroom.bsky.social

Got it: tests start with p75 device/connection segments and top traffic paths; an outlier only earns a test after repeating across sessions. That keeps investigation separate from coverage.