-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Ability to add custom annotations to trace files #30433
Comments
Feature originally proposed here: #28206 That issue's log also suggests that the only way to have custom annotations currently is to use javascripts' test framework. |
Is your request about particular non-JS Playwright versions or about support for such annotations in the playwright js library (as opposed to Playwright Test where you can already achieve it)? |
@yury-s it is about particular non-JS Playwright, specifically playwright-python. |
this has been raised on playwright-python: microsoft/playwright-python#1949 |
Folding into microsoft/playwright-python#1949 |
馃殌 Feature Request
I would like to propose a feature for the Playwright tracing facility that allows users to add custom annotations (free text) to trace files. Currently, Playwright's tracing capabilities automatically record actions like page.navigate, page.click, etc. While this is incredibly useful, the ability to insert custom annotations would enhance the trace's usefulness and readability, especially for complex scenarios.
Example
Motivation
In many testing and debugging scenarios, it's beneficial to have context-specific information that explains why certain actions are taken or to mark important checkpoints in the trace. Custom annotations can serve as explanatory notes or markers within the trace file, making it easier to understand the flow, especially when sharing these traces with other team members.
For instance, a test might involve a series of steps with conditional logic, and being able to annotate the trace with information like "Starting Section A tests" or "Conditional logic X triggered" would be valuable.
The text was updated successfully, but these errors were encountered: