⚡ Sangsakala Proxy 🏠 Home
Skip to content

Playwright - add java sources to a captured Playwright trace - #1450

Open
antonfilichkin wants to merge 2 commits into
allure-framework:mainfrom
antonfilichkin:feat/playwright-trace-sources-flag
Open

antonfilichkin wants to merge 2 commits into
allure-framework:mainfrom
antonfilichkin:feat/playwright-trace-sources-flag

Conversation

@antonfilichkin

@antonfilichkin antonfilichkin commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

Context

Allows attaching java sources to Playwright traces.

Allure only configures Playwright traces to include screenshots and snapshots via

new Tracing.StartOptions()
    .setScreenshots(true)
    .setSnapshots(true)

Playwright allows including java sources by setting PLAYWRIGHT_JAVA_SRC and configuring tracing via

new Tracing.StartOptions()
    .setSources(true)

The problem:

  1. Playwright provides trace as .zip binary
  2. Playwright doesn't have mechanism to suppress synthetic frames from trace, it only handles its own ones. But with Allure enabled - frame 0 is always synthetic AspectJ-weaving glue inserted by AllurePlaywrightAspect, not the real caller - making Trace Viewer's Source tab useless.
  3. Playwright handles trace building on it's binary side

The idea is to add configurable option to allow Allure rewrite sources and remove it's own synthetic frames
Implementation idea:

  • Add allure.playwright.trace.sources (default false) to opt into embedding sources in the trace.
  • Add TraceStackSourceTrimmer, which rewrites the trace.stacks entry in place: it resolves the first file-backed frame in each stack, falling back to stripping the leading run of recognizable AspectJ/Playwright weaving frames when no frame resolves. Fails open on any error, leaving the trace attached unchanged. With some short-circuits to disable zip/json processing - I.e. binary blobs, sources path not set.

Trace examples (both with sources)
Screenshot 2026-09-21 at 12 07 30
npx playwright show-trace trace-after.zip
trace-before.zip
trace-after.zip

Checklist

…spectJ frames from trace stacks

Playwright's Tracing.StartOptions#setSources embeds a stack per action, but
frame 0 is always synthetic AspectJ-weaving glue inserted by
AllurePlaywrightAspect, not the real caller - making Trace Viewer's Source
tab useless without this.

- Add allure.playwright.trace.sources (default false) to opt into embedding
  sources in the trace.
- Add TraceStackSourceTrimmer, which rewrites the trace.stacks entry in
  place: it resolves the first file-backed frame in each stack, falling
  back to stripping the leading run of recognizable AspectJ/Playwright
  weaving frames when no frame resolves. Fails open on any error, leaving
  the trace attached unchanged.
- Declare the module's new compile-time-only dependency on Gson in
  module-info.java.
@baev
baev requested review from a team and andrcuns and removed request for a team November 2, 2026 17:19

@andrcuns andrcuns left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the submission @antonfilichkin

My java is very rusty (almost non existent at this point 😅 ) but an agent review found a few issues, could you please check?

if (!AllurePlaywrightConfig.shouldEmbedTraceSources()) {
return false;
}
if (Objects.isNull(System.getenv(PLAYWRIGHT_JAVA_SRC))) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] Do not disable valid per-instance Playwright source configuration

Playwright also accepts source roots through Playwright.create(new Playwright.CreateOptions().setEnv(Map.of("PLAYWRIGHT_JAVA_SRC", sourceRoot))); the variable does not have to exist in the JVM's process environment. With this supported configuration and allure.playwright.trace.sources=true, this check returns false, so startTracing() sets sources=false and skips trimming.

I reproduced the mismatch against Playwright 1.62.0: its real StackTraceCollector.createFromEnv() accepts the instance configuration, while the Allure helper passes StartOptions.sources=false. The new real-trace test uses this same setEnv() mechanism, but starts tracing directly rather than through AllurePlaywright.startTracing(), so it does not cover this failure.

Please let the opt-in property enable source embedding without requiring System.getenv() to contain the source roots, and cover the per-instance configuration through the public helper.

ZipEntry entry;
while ((entry = zis.getNextEntry()) != null) {
final String name = entry.getName();
final byte[] content = readAll(zis);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] Stream unchanged entries instead of buffering every decompressed resource

This reads every ZIP entry fully into heap, including screenshots and captured network response bodies, even though only trace.stacks needs transformation. ByteArrayOutputStream grows an unbounded backing array and toByteArray() then allocates another full copy. The resources/ handling below does not skip this allocation.

I reproduced an uncaught OutOfMemoryError in TraceStackSourceTrimmer.readAll() using a 49,237-byte ZIP containing a 48 MiB resource and a valid trace.stacks entry, with a 64 MiB child-JVM heap. Neither this class nor DefaultTraceSession.stop() catches that error, so trace diagnostics can disrupt test execution instead of failing open and attaching the original archive.

Please copy unchanged entries with bounded memory, buffering only the stack JSON. Preserving their original compressed payloads would also avoid unnecessary decompression.

if (stored) {
final CRC32 crc = new CRC32();
crc.update(content);
outEntry.setMethod(ZipEntry.STORED);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] Preserve compression for text resources

Every resources/ entry reaches this branch, but that directory contains compressible HTML, JavaScript, JSON response bodies, and embedded Java sources, not only already-compressed screenshots. Writing all of them as STORED can substantially increase the trace attachment size.

Running this trimmer on the PR's own trace-before.zip increased the archive from 17,968 to 28,554 bytes (about 59%). Its HTML resource alone expanded from 2,301 compressed bytes to 6,639 stored bytes. Larger or text-heavy traces will incur unnecessary attachment storage, transfer, and loading costs.

Please preserve unchanged entries' compressed payloads, or at least retain compression for compressible resources rather than treating the entire resources/ directory as incompressible binary data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants