Repository navigation
feat(reporter): report step params in the chrome://tracing report - #42358
Pavel Feldman (pavelfeldman) merged 1 commit into
Conversation
73a24c5 to
31a44e5
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Step params reported to the reporters land in the `params` trace event argument of the corresponding slice. Render the API call params through a class/method-aware switch keyed the same way as the protocol metainfo, so that each call reports the arguments that say what it did. Unbounded arguments are never reported and long strings are truncated to keep the reports small. Write the report event by event instead of serializing it into a single string, and stream it through gzip when the output file ends with ".gz".
31a44e5 to
10dd270
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Test results for "tests 1"4 flaky51370 passed, 1238 skipped Merge workflow run. |
Test results for "MCP"1 failed 8141 passed, 1361 skipped Merge workflow run. |
|
Hi, I'm the Playwright bot and I took a look at the CI failures here. 🟡 One failure, but I can't tie it to this PR either way
DetailsThe latest merged reports: Uncertain
Flaky / infra
Triaged by the Playwright bot - agent run |
d4e1023
into
microsoft:main
Summary
TestStep.paramsnow land in theparamstrace event argument of the corresponding slice, sochrome://tracingshows the locator, url andtest.stepparams next to each step.