To get the most out of your logging with the RP agent and Playwright API, you'll want to use Playwright's trace viewer. This tool gives you a detailed view of your tests, including actions, timing, parameters, return values, and logs.
When running tests locally, start recording a trace by setting the --trace
flag to "on". Use the command npx playwright test --trace on
.
npx playwright test --trace on
This records traces for each test and generates an HTML report.
For tests on continuous integration (CI), configure traces to run on the first retry of a failed test. Set the trace: 'on-first-retry'
option in your test configuration file (playwright.config.ts
).
module.exports = {
use: {
trace: 'on-first-retry',
},
};
This produces a trace.zip
file for each retried test.
The trace viewer lets you inspect your tests in detail. You can see actions, their time and duration, console output, network requests, and source code.
By integrating the Playwright trace viewer with RP Agent logging, you get detailed logging while still benefiting from Playwright API's other features.
Remember, this advice is based on the information provided. If you have specific requirements or constraints not covered here, please provide more context.
If you still have questions, please ask a question and I will try to answer it.
Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email [email protected].