From cba8c3c54c1431fda2294857a072d5da384d502b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dar=C3=ADo=20Kondratiuk?= <dariokondratiuk@gmail.com>
Date: Thu, 12 Feb 2026 12:20:49 -0300
Subject: [PATCH 1/2] Migrate from postData to postDataEntries in
 CdpHttpRequest

Use postDataEntries (base64-encoded) from CDP protocol instead of the
deprecated postData field. Falls back to postData when entries are missing.

Ports upstream puppeteer PR #14640.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---
 .../NetworkTests/CdpHttpRequestTests.cs       | 78 +++++++++++++++++++
 lib/PuppeteerSharp/Cdp/CdpHttpRequest.cs      | 26 ++++++-
 .../Cdp/Messaging/PostDataEntry.cs            |  6 ++
 lib/PuppeteerSharp/Cdp/Messaging/Request.cs   |  2 +
 4 files changed, 111 insertions(+), 1 deletion(-)
 create mode 100644 lib/PuppeteerSharp.Tests/NetworkTests/CdpHttpRequestTests.cs
 create mode 100644 lib/PuppeteerSharp/Cdp/Messaging/PostDataEntry.cs

diff --git a/lib/PuppeteerSharp.Tests/NetworkTests/CdpHttpRequestTests.cs b/lib/PuppeteerSharp.Tests/NetworkTests/CdpHttpRequestTests.cs
new file mode 100644
index 000000000..47bccbb5d
--- /dev/null
+++ b/lib/PuppeteerSharp.Tests/NetworkTests/CdpHttpRequestTests.cs
@@ -0,0 +1,78 @@
+using System;
+using System.Collections.Generic;
+using System.Net.Http;
+using Microsoft.Extensions.Logging;
+using NSubstitute;
+using NUnit.Framework;
+using PuppeteerSharp.Cdp;
+using PuppeteerSharp.Cdp.Messaging;
+
+namespace PuppeteerSharp.Tests.NetworkTests;
+
+[TestFixture]
+public class CdpHttpRequestTests
+{
+    [Test]
+    public void ShouldReconstructPostDataFromPostDataEntries()
+    {
+        var client = Substitute.For<CDPSession>();
+        var frame = Substitute.For<IFrame>();
+        using var loggerFactory = new LoggerFactory();
+
+        var request = new CdpHttpRequest(
+            client,
+            frame,
+            "interceptionId",
+            true,
+            new RequestWillBeSentResponse
+            {
+                RequestId = "requestId",
+                Request = new Request
+                {
+                    Url = "http://example.com",
+                    Method = HttpMethod.Post,
+                    Headers = new Dictionary<string, string>(),
+                    PostDataEntries =
+                    [
+                        new PostDataEntry { Bytes = Convert.ToBase64String(System.Text.Encoding.UTF8.GetBytes("part1")) },
+                        new PostDataEntry { Bytes = Convert.ToBase64String(System.Text.Encoding.UTF8.GetBytes("part2")) },
+                    ],
+                },
+                Initiator = new Initiator { Type = InitiatorType.Other },
+            },
+            [],
+            loggerFactory);
+
+        Assert.That(request.PostData, Is.EqualTo("part1part2"));
+    }
+
+    [Test]
+    public void ShouldFallbackToPostDataIfPostDataEntriesIsMissing()
+    {
+        var client = Substitute.For<CDPSession>();
+        var frame = Substitute.For<IFrame>();
+        using var loggerFactory = new LoggerFactory();
+
+        var request = new CdpHttpRequest(
+            client,
+            frame,
+            "interceptionId",
+            true,
+            new RequestWillBeSentResponse
+            {
+                RequestId = "requestId",
+                Request = new Request
+                {
+                    Url = "http://example.com",
+                    Method = HttpMethod.Post,
+                    Headers = new Dictionary<string, string>(),
+                    PostData = "originalData",
+                },
+                Initiator = new Initiator { Type = InitiatorType.Other },
+            },
+            [],
+            loggerFactory);
+
+        Assert.That(request.PostData, Is.EqualTo("originalData"));
+    }
+}
diff --git a/lib/PuppeteerSharp/Cdp/CdpHttpRequest.cs b/lib/PuppeteerSharp/Cdp/CdpHttpRequest.cs
index 92567622d..f36a0b439 100644
--- a/lib/PuppeteerSharp/Cdp/CdpHttpRequest.cs
+++ b/lib/PuppeteerSharp/Cdp/CdpHttpRequest.cs
@@ -42,7 +42,7 @@ internal CdpHttpRequest(
         Url = data.Request.Url + (data.Request.UrlFragment ?? string.Empty);
         ResourceType = data.Type ?? ResourceType.Other;
         Method = data.Request.Method;
-        PostData = data.Request.PostData;
+        PostData = ReconstructPostData(data.Request);
         HasPostData = data.Request.HasPostData ?? false;
 
         Frame = frame;
@@ -283,6 +283,30 @@ internal override async Task FinalizeInterceptionsAsync()
     internal override void EnqueueInterceptionActionCore(Func<IRequest, Task> pendingHandler)
         => _interceptHandlers.Add(pendingHandler);
 
+    private static string ReconstructPostData(Messaging.Request request)
+    {
+        if (request.PostDataEntries is { Length: > 0 })
+        {
+            var buffers = request.PostDataEntries
+                .Where(entry => entry.Bytes != null)
+                .Select(entry => Convert.FromBase64String(entry.Bytes))
+                .ToArray();
+
+            var totalLength = buffers.Sum(b => b.Length);
+            var merged = new byte[totalLength];
+            var offset = 0;
+            foreach (var buffer in buffers)
+            {
+                Buffer.BlockCopy(buffer, 0, merged, offset, buffer.Length);
+                offset += buffer.Length;
+            }
+
+            return Encoding.UTF8.GetString(merged);
+        }
+
+        return request.PostData;
+    }
+
     private Header[] HeadersArray(Dictionary<string, string> headers)
         => headers?.Select(pair => new Header { Name = pair.Key, Value = pair.Value }).ToArray();
 
diff --git a/lib/PuppeteerSharp/Cdp/Messaging/PostDataEntry.cs b/lib/PuppeteerSharp/Cdp/Messaging/PostDataEntry.cs
new file mode 100644
index 000000000..308cd6e40
--- /dev/null
+++ b/lib/PuppeteerSharp/Cdp/Messaging/PostDataEntry.cs
@@ -0,0 +1,6 @@
+namespace PuppeteerSharp.Cdp.Messaging;
+
+internal class PostDataEntry
+{
+    public string Bytes { get; set; }
+}
diff --git a/lib/PuppeteerSharp/Cdp/Messaging/Request.cs b/lib/PuppeteerSharp/Cdp/Messaging/Request.cs
index ab3741788..0cf168cb7 100644
--- a/lib/PuppeteerSharp/Cdp/Messaging/Request.cs
+++ b/lib/PuppeteerSharp/Cdp/Messaging/Request.cs
@@ -42,4 +42,6 @@ internal class Request
     public string UrlFragment { get; set; }
 
     public bool? HasPostData { get; set; }
+
+    public PostDataEntry[] PostDataEntries { get; set; }
 }

From 4b351e53417cbc5832d2f66ca1926366f24bb415 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dar=C3=ADo=20Kondratiuk?= <dariokondratiuk@gmail.com>
Date: Thu, 12 Feb 2026 12:46:58 -0300
Subject: [PATCH 2/2] Migrate commands to skills & add PuppeteerTest attributes

- Migrate implement-upstream-change and implement-bidi-feature from
  .claude/commands/ to .claude/skills/ format
- Add PuppeteerTest attributes to CdpHttpRequestTests to match upstream
- Remove obsolete .github/agents/ definitions

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---
 .claude/commands/implement-upstream-change.md |  17 -
 .../implement-bidi-feature/SKILL.md}          |   0
 .../skills/implement-upstream-change/SKILL.md |  46 ++
 .github/agents/bidi-migration.md              | 131 -----
 .github/agents/puppeteer-sharp-main-agent.md  | 482 ------------------
 .../NetworkTests/CdpHttpRequestTests.cs       |   5 +-
 6 files changed, 49 insertions(+), 632 deletions(-)
 delete mode 100644 .claude/commands/implement-upstream-change.md
 rename .claude/{commands/implement-bidi-feature.md => skills/implement-bidi-feature/SKILL.md} (100%)
 create mode 100644 .claude/skills/implement-upstream-change/SKILL.md
 delete mode 100644 .github/agents/bidi-migration.md
 delete mode 100644 .github/agents/puppeteer-sharp-main-agent.md

diff --git a/.claude/commands/implement-upstream-change.md b/.claude/commands/implement-upstream-change.md
deleted file mode 100644
index 08ce323cf..000000000
--- a/.claude/commands/implement-upstream-change.md
+++ /dev/null
@@ -1,17 +0,0 @@
-# Context
-You are a software developer integrating changes from a project written in TypeScript into a .NET project.
-We call upstream to the original typescript project.
-
-# Task
-
-You are going to check the changes on the PR $ARGUMENTS
-You will find the upstream repository at ../../puppeteer/puppeteer. Feel free to read the code there and even make git action to bring the changes you need to evaluate.
-
-Once you have all the context, you will implement the same changes in this .NET project.
-You will create a new branch named `implement-upstream-change-<PR_NUMBER>` where `<PR_NUMBER>` is the number of the PR you are implementing.
-You will have to implement the code as close as possible to the original code, but adapted to .NET idioms and practices.
-
-As part of the task you will need to generate a document explaining the changes you made, and how they relate to the original PR.
-
-You need to run related tests to ensure everything is working as expected.
-If tests are failing, you will need to fix them.
diff --git a/.claude/commands/implement-bidi-feature.md b/.claude/skills/implement-bidi-feature/SKILL.md
similarity index 100%
rename from .claude/commands/implement-bidi-feature.md
rename to .claude/skills/implement-bidi-feature/SKILL.md
diff --git a/.claude/skills/implement-upstream-change/SKILL.md b/.claude/skills/implement-upstream-change/SKILL.md
new file mode 100644
index 000000000..3fffb22c3
--- /dev/null
+++ b/.claude/skills/implement-upstream-change/SKILL.md
@@ -0,0 +1,46 @@
+# Context
+You are a software developer integrating changes from a project written in TypeScript into a .NET project.
+We call upstream to the original typescript project.
+
+# Task
+
+You are going to check the changes on the PR $ARGUMENTS
+You will find the upstream repository at ../../puppeteer/puppeteer. Feel free to read the code there and even make git actions to bring the changes you need to evaluate.
+
+Once you have all the context, you will implement the same changes in this .NET project.
+
+## Git Workflow
+
+1. Fetch the latest from origin: `git fetch origin`
+2. Create a new branch from `origin/master` named `implement-upstream-change-<PR_NUMBER>` where `<PR_NUMBER>` is the number of the PR you are implementing: `git checkout -b implement-upstream-change-<PR_NUMBER> origin/master`
+3. Implement all the changes (see below)
+4. Commit your changes with a descriptive message
+5. Push the branch: `git push -u origin implement-upstream-change-<PR_NUMBER>`
+6. Create a PR via `gh pr create` targeting `master`
+
+## Implementation
+
+You will have to implement the code as close as possible to the original code, but adapted to .NET idioms and practices.
+
+### Porting Tests
+
+All tests brought from upstream **must** use the `[Test, PuppeteerTest(...)]` attribute header. The attribute signature is:
+
+```csharp
+[Test, PuppeteerTest("<spec-file>", "<describes chain>", "<test-name>")]
+```
+
+- `<spec-file>`: the upstream `.spec.ts` filename (e.g. `"network.spec"`).
+- `<describes chain>`: the nested `describe` block titles joined, matching the upstream structure (e.g. `"network"`).
+- `<test-name>`: the `it(...)` test title from upstream (e.g. `"should set bodySize and headersSize"`).
+
+Look at existing tests in the project for reference on how these attributes are used.
+
+## Verification
+
+You need to run related tests to ensure everything is working as expected.
+If tests are failing, you will need to fix them.
+
+## Summary
+
+As part of the task you will need to generate a document explaining the changes you made, and how they relate to the original PR.
diff --git a/.github/agents/bidi-migration.md b/.github/agents/bidi-migration.md
deleted file mode 100644
index c2414d973..000000000
--- a/.github/agents/bidi-migration.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-name: Bidi migration
-description: Implement bidi code
----
-
-# Context
-You are a software developer integrating changes from a project written in TypeScript into a .NET project.
-We call upstream to the original typescript project.
-This task should use the **v21 branch** as base branch and to create pull requests.
-Use the puppeteer-sharp/lib/CLAUDE.md for project context.
-
-## Upstream Repositories
-- Upstream puppeteer: https://github.com/puppeteer/puppeteer/
-- Upstream webdriver bidi: https://github.com/webdriverbidi-net/webdriverbidi-net
-
-Clone these if needed to reference implementation:
-```bash
-cd /home/runner/work
-git clone --depth 1 https://github.com/puppeteer/puppeteer.git
-git clone --depth 1 https://github.com/webdriverbidi-net/webdriverbidi-net.git
-```
-
-# Task
-
-You are going to implement the changes to make $ARGUMENTS pass.
-
-## Step-by-Step Process
-
-1. **Find and analyze the test expectation**
-   - Location: `lib/PuppeteerSharp.Nunit/TestExpectations/TestExpectations.local.json`
-   - Find the entry with `testIdPattern` matching $ARGUMENTS
-   - Note: The pattern may not exist exactly as specified. Check for broader patterns that include it.
-   - Example: If looking for `[jshandle.spec] *.evaluateHandle*`, you might find `[jshandle.spec] *` instead
-
-2. **Locate matching tests**
-   - Tests are in `lib/PuppeteerSharp.Tests/`
-   - Look for `[Test, PuppeteerTest("spec-file", "category", "test-name")]` attributes
-   - Pattern matching examples:
-     - `[jshandle.spec] *.evaluateHandle*` matches: `[Test, PuppeteerTest("jshandle.spec", "JSHandle Page.evaluateHandle", "should work")]`
-     - `[chromiumonly.spec] Chromium-Specific *` matches: `[Test, PuppeteerTest("chromiumonly.spec", "Chromium-Specific Page Tests", "...")]`
-
-3. **Check if implementation already exists**
-   - **IMPORTANT**: Many features may already be implemented! Check the code BEFORE making changes.
-   - BiDi implementations are in `lib/PuppeteerSharp/Bidi/`
-   - Key files to check:
-     - `BidiRealm.cs` - Main realm implementation  
-     - `BidiJSHandle.cs` - JSHandle for BiDi
-     - `BidiElementHandle.cs` - ElementHandle for BiDi
-     - `BidiFrame.cs` - Frame for BiDi
-   - Base implementations are in `lib/PuppeteerSharp/`
-   - If the feature is already implemented, document this in the PR description
-
-4. **Reference upstream implementation** (if code changes needed)
-   - Puppeteer TypeScript: `/home/runner/work/puppeteer/packages/puppeteer-core/src/`
-   - BiDi-specific code: `/home/runner/work/puppeteer/packages/puppeteer-core/src/bidi/`
-   - Test files: `/home/runner/work/puppeteer/test/src/`
-   - WebDriver BiDi .NET: `/home/runner/work/webdriverbidi-net/`
-
-5. **Implement or verify the code**
-   - Port TypeScript to C# using .NET idioms
-   - Match the upstream logic as closely as possible
-   - Common patterns:
-     - TypeScript `async methodName(...args): Promise<Type>` → C# `Task<Type> MethodNameAsync(params object[] args)`
-     - TypeScript `using` (explicit resource management) → C# `await using` / `IAsyncDisposable`
-     - Handle delegation: JSHandle methods often delegate to Realm with handle as first argument
-
-6. **Update test expectations**
-   - If feature is working, remove or refine the test expectation entry
-   - Be careful with broad patterns like `[jshandle.spec] *` - only remove if ALL tests pass
-   - Consider creating more specific patterns if only some tests work
-
-7. **Document in PR description** (NOT in separate files)
-   - **Do NOT create IMPLEMENTATION_NOTES.md, SUMMARY.md, or similar documentation files**
-   - Put ALL implementation details, analysis, and findings in the PR description
-   - Include:
-     - What tests are affected
-     - Implementation status (already working, new code added, or partially working)
-     - Key code components involved
-     - Comparison with upstream TypeScript if relevant
-
-8. **Test verification**
-   - Run tests with: `BROWSER=FIREFOX PROTOCOL=webDriverBiDi dotnet test --filter "TestName"`
-   - Build first if needed: `dotnet build lib/PuppeteerSharp.sln`
-   - Note: May need self-signed certificate for test server (see setup below)
-
-## Important Notes
-
-- **Start from v21 branch**: Always checkout v21 first before creating your feature branch
-- **Check existing code**: Many features are already implemented - verify before making changes
-- **No separate docs**: All documentation goes in the PR description, not in separate markdown files
-- **Test patterns**: Use wildcards to match multiple tests, be careful with broad patterns
-- **BiDi vs CDP**: This is for WebDriver BiDi protocol (Firefox), not Chrome DevTools Protocol
-
-## Setup Requirements
-
-If building/testing is needed:
-
-**Self-signed certificate for test server:**
-```bash
-cd lib/PuppeteerSharp.TestServer
-openssl req -x509 -newkey rsa:2048 -keyout testKey.pem -out testCert.cer -days 365 -nodes -subj "/CN=localhost"
-```
-
-**Update .gitignore** to exclude test certificates:
-```
-lib/PuppeteerSharp.TestServer/testKey.pem
-lib/PuppeteerSharp.TestServer/testCert.cer
-```
-
-## Code Structure Reference
-
-```
-lib/PuppeteerSharp/
-├── Bidi/                      # BiDi protocol implementations
-│   ├── BidiRealm.cs          # Main realm - handles evaluation
-│   ├── BidiJSHandle.cs       # JSHandle for BiDi
-│   ├── BidiElementHandle.cs  # ElementHandle for BiDi
-│   ├── BidiFrame.cs          # Frame for BiDi
-│   └── Core/                 # Core BiDi protocol classes
-├── JSHandle.cs               # Base JSHandle class
-├── Realm.cs                  # Base Realm class
-└── IJSHandle.cs              # JSHandle interface
-
-lib/PuppeteerSharp.Tests/
-├── JSHandleTests/            # JSHandle tests
-├── FrameTests/               # Frame tests
-└── ...                       # Other test directories
-
-lib/PuppeteerSharp.Nunit/TestExpectations/
-└── TestExpectations.local.json  # Test expectations to modify
-```
diff --git a/.github/agents/puppeteer-sharp-main-agent.md b/.github/agents/puppeteer-sharp-main-agent.md
deleted file mode 100644
index 544fd77fa..000000000
--- a/.github/agents/puppeteer-sharp-main-agent.md
+++ /dev/null
@@ -1,482 +0,0 @@
----
-name: Puppeteer-Sharp main agent
-description: Puppeteer-sharp expert
----
-
-# PuppeteerSharp Codebase Overview
-
-PuppeteerSharp is a C# library for automating Chromium-based browsers and Firefox. It provides a high-level API to control browsers via the DevTools Protocol (CDP) and WebDriver BiDi protocol.
-
-## Goal
-
-The goal of this project is to port the popular Node.js Puppeteer library to .NET.
-Everything in PuppeteerSharp is inspired by the original Puppeteer library, but adapted to C# idioms and .NET practices.
-
-## External Sources:
-These external sources are referenced or used as inspiration in the codebase. Feel free to explore them for a deeper understanding.
-You may run git commands to update these repositories locally.
-
-- Original Puppeteer repository: https://github.com/puppeteer/puppeteer/. Every time "upstream" is mentioned, we are referring to this code.
-- Bidi Driver: https://github.com/webdriverbidi-net/webdriverbidi-net
-
-## Upstream code structure
-
-- Code in upstream puppeteer-core/src/api/* are our abstract class. For instanc,e our public abstract class Frame.
-- Code in upstream puppeteer-core/src/bidi/* are our Bidi* classes.
-- Code in upstream puppeteer-core/src/cdp/* are our Cdp* classes.
-
-## Project Structure
-
-```
-lib/
-├── PuppeteerSharp/                 # Main library
-│   ├── Bidi/                       # WebDriver BiDi protocol implementation (45 files)
-│   ├── Cdp/                        # Chrome DevTools Protocol implementation (204 files)
-│   ├── Transport/                  # Communication layer (WebSocket, etc.)
-│   ├── Helpers/                    # Utility functions and extensions
-│   ├── Input/                      # Keyboard, Mouse, Touchscreen input handling
-│   ├── Media/                      # Screenshot, PDF, viewport options
-│   ├── Mobile/                     # Device descriptors and emulation
-│   ├── PageAccessibility/          # Accessibility tree and ARIA handling
-│   ├── PageCoverage/               # Code coverage tracking
-│   ├── QueryHandlers/              # CSS, XPath, Pierce, Text selectors
-│   ├── BrowserData/                # Browser version and channel management
-│   ├── States/                     # Process state machine
-│   ├── Injected/                   # JavaScript to be injected into pages
-│   └── *.cs                        # Core classes (Browser, Page, Frame, etc.)
-├── PuppeteerSharp.Tests/           # 58+ test categories (~45k+ test files)
-├── PuppeteerSharp.Nunit/           # NUnit test framework integration
-├── PuppeteerSharp.TestServer/      # Local HTTP server for testing
-├── PuppeteerSharp.TestServer/wwwroot/ # Test fixtures and assets
-├── demo/                           # Demo application
-└── PuppeteerSharp.sln              # Solution file
-```
-
-## Key Architecture Patterns
-
-### Dual Protocol Support: CDP vs BiDi
-
-PuppeteerSharp supports two browser automation protocols:
-
-1. **Chrome DevTools Protocol (CDP)**:
-   - Implemented in: `CdpBrowser`, `CdpPage`, `CdpFrame`, `CdpTarget`, etc.
-   - CDP-specific implementation classes
-   - Used for Chromium-based browsers and Firefox
-   - Classes: `CdpJSHandle`, `CdpElementHandle`, `CdpKeyboard`, `CdpMouse`, etc.
-
-2. **WebDriver BiDi Protocol**:
-   - Implemented in: `BidiBrowser`, `BidiPage`, `BidiFrame`, `BidiTarget`, etc.
-   - Newer, more standardized protocol
-   - Lower-level core implementations in `Bidi/Core/` directory
-   - Classes: `BidiJSHandle`, `BidiElementHandle`, `BidiMouse`, etc.
-   - Events: `BidiBrowsingContextEventArgs`, `UserPromptEventArgs`, `ResponseEventArgs`, etc.
-
-### Protocol Abstraction Pattern
-
-The library uses a base class pattern with protocol-specific implementations:
-
-- **Interface Level**: `IBrowser`, `IPage`, `IFrame`, `IRequest`, `IResponse`
-- **Abstract Base Classes**: `Browser`, `Page`, `Frame`, `Request<TResponse>`, `Response<TRequest>`
-- **Protocol Implementations**: `CdpBrowser`/`BidiBrowser`, `CdpPage`/`BidiPage`, etc.
-
-This design allows code to work with either protocol transparently through interfaces.
-
-## Core Components
-
-### 1. Entry Point: Puppeteer Static Class
-- **File**: `/PuppeteerSharp/Puppeteer.cs`
-- **Key Methods**:
-  - `LaunchAsync(LaunchOptions)`: Launch a browser instance
-  - `ConnectAsync(ConnectOptions)`: Connect to existing browser
-  - `GetDefaultArgs()`: Get default browser launch arguments
-  - Static properties: `Devices`, `NetworkConditions`, `ExtraJsonSerializerContext`
-
-### 2. Browser Management
-
-#### `Launcher` Class
-- Determines which browser to launch (Chrome, Chromium, Firefox)
-- Resolves executable path
-- Creates appropriate launcher (`ChromeLauncher` or `FirefoxLauncher`)
-- Handles process lifecycle
-
-#### `IBrowser` Interface & `Browser` Abstract Class
-- **Key Properties**:
-  - `WebSocketEndpoint`: Connection URL
-  - `BrowserType`: Chrome, Chromium, or Firefox
-  - `DefaultContext`: Default browser context
-  - `DefaultWaitForTimeout`: Global timeout setting
-- **Key Methods**:
-  - `NewPageAsync()`: Create new page
-  - `CreateBrowserContextAsync()`: Create isolated context
-  - `Targets()`: Get all targets (pages, workers, etc.)
-  - `PagesAsync()`: Get all pages across contexts
-  - `GetVersionAsync()`: Browser version
-  - `Disconnect()`: Disconnect from browser
-
-### 3. Page Model
-
-#### `IPage` Interface & `Page` Abstract Class
-- **Key Properties**:
-  - `MainFrame`: Primary frame
-  - `Frames`: All frames in page
-  - `Url`: Current URL
-  - `Workers`: Web workers
-  - `Keyboard`, `Mouse`, `Touchscreen`: Input devices
-- **Key Events**: (40+ events)
-  - `Close`, `Load`, `DOMContentLoaded`
-  - `Console`, `Dialog`, `Error`, `PageError`
-  - `Request`, `Response`, `RequestFailed`, `RequestFinished`
-  - `FrameAttached`, `FrameDetached`, `FrameNavigated`
-- **Key Methods**:
-  - `GoToAsync()`: Navigate to URL
-  - `ScreenshotAsync()`: Capture page screenshot
-  - `PdfAsync()`: Generate PDF
-  - `EvaluateAsync()`: Execute JavaScript
-  - `WaitForNavigationAsync()`: Wait for navigation
-  - `WaitForSelectorAsync()`: Wait for element
-  - `InterceptRequestAsync()`: Intercept network requests
-
-### 4. Frame Model
-
-#### `IFrame` Interface & `Frame` Abstract Class
-- Represents an `<iframe>` or main document
-- Lifecycle events: attached → navigated → detached
-- Similar evaluation and waiting methods as Page
-- **Key Methods**:
-  - `ChildFrames`: Get nested frames
-  - `ParentFrame`: Get parent frame
-  - `EvaluateAsync()`, `EvaluateFunctionAsync()`: Execute code
-  - `WaitForSelectorAsync()`: Wait for elements
-  - `QuerySelectorAsync()`, `QuerySelectorAllAsync()`: Find elements
-
-### 5. Element Handling
-
-#### Handle Hierarchy
-- `IJSHandle` (Interface): Represents object in browser
-- `JSHandle` (Abstract): Base implementation
-- `CdpJSHandle` / `BidiJSHandle`: Protocol-specific implementations
-- `IElementHandle` (Interface): Represents DOM element
-- `ElementHandle` (Abstract): Element-specific operations
-- `CdpElementHandle` / `BidiElementHandle`: Protocol-specific implementations
-
-#### `ElementHandle` Capabilities
-- **Selection**: `QuerySelectorAsync()`, `QuerySelectorAllAsync()`, `EvaluateAsync()`
-- **Interaction**: `ClickAsync()`, `TypeAsync()`, `PressAsync()`
-- **Properties**: `BoundingBoxAsync()`, `BoxModelAsync()`, `ScreenshotAsync()`
-- **Forms**: `UploadFileAsync()`, `SelectAsync()`
-- **Drag & Drop**: `DragAsync()`, `DragAndDropAsync()`
-
-### 6. Network Management
-
-#### Request/Response Model
-- **Request**:
-  - Abstract base: `Request<TResponse>`
-  - Implementations: `CdpHttpRequest`, `BidiHttpRequest`
-  - Properties: URL, headers, method, post data, resource type
-  - Methods: `ContinueAsync()`, `AbortAsync()`, `RespondAsync()`
-
-- **Response**:
-  - Abstract base: `Response<TRequest>`
-  - Implementations: `CdpHttpResponse`, `BidiHttpResponse`
-  - Methods: `TextAsync()`, `JsonAsync()`, `BufferAsync()`
-  - Properties: Status code, headers, URL
-
-#### Interception
-- `InterceptRequestAsync()`: Register request handler
-- Request properties and methods for control
-- Redirect chain tracking
-- Initiator information
-
-### 7. Communication Layer
-
-#### Transport (`Transport/` directory)
-- `IConnectionTransport`: Abstract transport interface
-- `WebSocketTransport`: WebSocket implementation
-- `MessageReceivedEventArgs`: Message event data
-- Handles binary message sending/receiving
-
-#### Connection (`Cdp/Connection.cs`)
-- `Connection` class: Manages CDP communication
-- Session management via `CdpCDPSession`
-- Message routing and callback handling
-- Error handling and protocol timeout
-
-#### CDPSession (`ICDPSession` interface)
-- Low-level protocol session
-- `SendAsync()`: Send CDP commands
-- Event subscriptions for CDP events
-- Methods for direct protocol access
-
-### 8. Execution Context & Script Evaluation
-
-#### Realm (Base Class)
-- Abstract: `Realm` (core evaluation base)
-- Manages execution contexts and script evaluation
-- Task manager for tracking ongoing operations
-
-#### IsolatedWorld
-- CDP-specific execution context implementation
-- Binding management for JavaScript callbacks
-- Context lifecycle handling
-- Frame and Worker association
-
-#### ExecutionContext
-- Represents a JavaScript execution environment
-- Methods for evaluation and handle adoption
-- Binding utilities for calling .NET from JS
-
-### 9. Input Handling
-
-#### Keyboard (`Input/`)
-- `IKeyboard` interface
-- `Keyboard` base class
-- `CdpKeyboard`, `BidiKeyboard` implementations
-- **Methods**: `PressAsync()`, `TypeAsync()`, `DownAsync()`, `UpAsync()`
-- Key definitions and special key handling
-
-#### Mouse (`Input/`)
-- `IMouse` interface
-- `Mouse` base class
-- `CdpMouse`, `BidiMouse` implementations
-- **Methods**: `MoveAsync()`, `ClickAsync()`, `DragAsync()`, `WheelAsync()`
-- Button types: Left, Right, Middle
-- Mouse state tracking
-
-#### Touchscreen (`Input/`)
-- `ITouchscreen` interface
-- `Touchscreen` base class
-- `CdpTouchscreen` implementation
-- **Methods**: `TapAsync()`, `TouchAsync()`
-
-### 10. Dialog Handling
-
-#### Dialog Classes
-- Abstract `Dialog` base class
-- `CdpDialog` (CDP implementation)
-- `BidiDialog` (BiDi implementation)
-- **Types**: alert, confirm, prompt, beforeunload
-- **Methods**: `Accept(string text)`, `Dismiss()`
-- Properties: `DialogType`, `Message`, `DefaultValue`
-
-### 11. File Handling
-
-#### FileChooser
-- Handles file input selection
-- `AcceptAsync()`: Select files for upload
-- `CancelAsync()`: Cancel file selection
-- Triggers on file input element interaction
-
-#### DeviceRequestPrompt
-- Handles device permission requests
-- Device info: name, model, type
-- Accept/reject operations
-
-### 12. Target Management
-
-#### ITarget Interface
-- Represents browser entity (page, iframe, worker, etc.)
-- Types: Page, WebWorker, Other
-- **Methods**: `PageAsync()`, `WorkerAsync()`, `AsPageAsync()`, `CreateCDPSessionAsync()`
-- URL, type, parent/child relationships
-
-#### Target Manager
-- `ITargetManager` interface
-- `ChromeTargetManager`: Chrome-specific target tracking
-- `FirefoxTargetManager`: Firefox-specific target tracking
-- Target lifecycle: discovered → created → destroyed
-
-### 13. Error Handling
-
-#### Exception Hierarchy
-- `PuppeteerException`: Base exception for all Puppeteer errors
-- `ProcessException`: Browser process issues
-- `TargetClosedException`: Target closed during operation
-- `TargetCrashedException`: Target crashed
-- `MessageException`: Protocol message errors
-- `SelectorException`: Selector parsing errors
-- `BufferException`: Buffer operation errors
-- `EvaluationFailedException`: Script evaluation errors
-- `WaitTaskTimeoutException`: Wait operation timeout
-
-### 14. Feature-Specific Modules
-
-#### PageAccessibility (`PageAccessibility/`)
-- `IAccessibility` interface
-- Accessibility tree snapshot
-- AXNode serialization
-- `SerializedAXNode`: Serialized accessibility data
-- Supports ARIA attributes
-
-#### PageCoverage (`PageCoverage/`)
-- `ICoverage` interface
-- JavaScript coverage tracking
-- CSS coverage tracking
-- Coverage entry with ranges
-- Function-level coverage support
-
-#### Media (`Media/`)
-- Viewport options, margins, clips
-- Screen orientation
-- Print media emulation
-- Screenshot options (type, quality, clip)
-- Print-to-PDF options
-
-#### Mobile (`Mobile/`)
-- Device descriptors (iPhone, iPad, etc.)
-- Pre-configured device profiles
-- Emulation settings: viewport, user agent, device scale factor
-- Touch support configuration
-
-### 15. Query Handlers (`QueryHandlers/`)
-- `CssQueryHandler`: CSS selector support
-- `XPathQueryHandler`: XPath expression support
-- `TextQueryHandler`: Text content matching
-- `PierceQueryHandler`: Shadow DOM piercing
-- `CustomQueryHandler`: User-defined handlers
-- Support for combined/nested selectors
-
-### 16. Browser Data Management
-
-#### BrowserData (`BrowserData/`)
-- Browser version tracking
-- Release channel information
-- Build ID management
-- Installed browser cache
-- Chrome and Firefox specifics
-- Version resolution and downloading
-
-### 17. Process State Management (`States/`)
-- State machine for browser process lifecycle
-- States: Initial → ProcessStarting → Started → Exiting → Exited → Disposed → Killing
-- `State` base class
-- `StateManager`: State transition handling
-- Proper cleanup and resource management
-
-## Testing Infrastructure
-
-### Test Organization (58+ categories)
-
-Test directory structure demonstrates comprehensive coverage:
-
-- **AccessibilityTests/**: Accessibility tree and AXNode testing
-- **BrowserContextTests/**: Context isolation and management
-- **BrowserTests/**: Browser lifecycle, context creation
-- **ClickTests/**: Element click operations
-- **CookiesTests/**: Cookie management
-- **CoverageTests/**: Code coverage tracking
-- **DeviceRequestPromptTests/**: Device permissions
-- **DialogTests/**: Alert, confirm, prompt dialogs
-- **DragAndDropTests/**: Drag and drop operations
-- **ElementHandleTests/**: Element interaction
-- **EmulationTests/**: Device and network emulation
-- **EvaluationTests/**: JavaScript evaluation
-- **FrameTests/**: Frame lifecycle and operations
-- **InputTests/**: Keyboard, mouse, touchscreen
-- **NetworkTests/**: Request/response interception
-- **PageTests/**: Page lifecycle, navigation, properties
-- **PrerenderTests/**: Prerendering capabilities
-- **RequestInterceptionTests/**: Request modification
-- **ScreenshotTests/**: Screenshot and PDF generation
-- **TracingTests/**: Performance tracing
-- Plus many more...
-
-### Test Infrastructure
-
-#### PuppeteerSharp.Nunit (`PuppeteerSharp.Nunit/`)
-- `PuppeteerTestAttribute`: Decorates tests with upstream metadata
-- Test expectations system (skip/fail/timeout conditions)
-- Platform-specific expectations (Win32, Linux, Darwin)
-- Browser-specific expectations (Chrome, Firefox)
-- Protocol-specific expectations (CDP, WebDriver BiDi)
-- Headless mode variations (headless, headful, headless-shell)
-- Local and upstream expectation merging
-- Tests should always match the code in upstream. Tests should never be changed to match the code local code.
-
-#### Upstream matching
-
-All our tests have this attribute `[Test, PuppeteerTest("screenshot.spec", "Screenshots Page.screenshot", "should take fullPage screenshots")]`
-This helps us link a test with the upstream test:
- * The first argument is the file upstream without the extension.
- * The second argument is the concatenation of `describe`s in upstream. In the example above it means that the test is inside two describes `Screenshots` and `Page.screenshot`.
- * The third argument is the test name.
-
-You shouldn't create tests that don't match upstream unless explicitly requested. In that case, the first argument should be `puppeteer-sharp`.
-
-**IMPORTANT: Test Expectations Files Rules:**
-- `TestExpectations.upstream.json`: This file should NEVER be edited unless syncing with the upstream Puppeteer project. It contains expectations that match the upstream Puppeteer test expectations.
-- `TestExpectations.local.json`: Use this file for local overrides and PuppeteerSharp-specific test expectations. Add entries here to skip or mark tests that fail due to .NET-specific issues or features not yet implemented.
-
-#### Test Server (`PuppeteerSharp.TestServer/`)
-- ASP.NET Core server for hosting test pages
-- wwwroot directory with test fixtures
-- Asset serving for test scenarios
-
-## Development Best Practices
-
-### Building and Running Tests
-
-When running tests, always build first and then use the `--no-build` flag to avoid rebuilding during test execution. This provides faster and more reliable test runs:
-Always be explicit with the browser and protocol you want to test using ENV variables BROWSER=FIREFOX|CHROME and PROTOCOL=bidi|cdp
-
-**IMPORTANT: Chrome should ALWAYS use CDP protocol. Firefox can use either CDP or BiDi.**
-
-```bash
-# Build the test project first with Firefox and BiDi
-BROWSER=FIREFOX PROTOCOL=bidi dotnet build PuppeteerSharp.Tests/PuppeteerSharp.Tests.csproj
-
-# Then run tests with --no-build flag
-BROWSER=FIREFOX PROTOCOL=bidi dotnet test PuppeteerSharp.Tests/PuppeteerSharp.Tests.csproj --filter "FullyQualifiedName~TestName" --no-build -- NUnit.TestOutputXml=TestResults
-
-# Chrome should ALWAYS use CDP protocol
-BROWSER=CHROME PROTOCOL=cdp dotnet build PuppeteerSharp.Tests/PuppeteerSharp.Tests.csproj && BROWSER=CHROME PROTOCOL=cdp dotnet test PuppeteerSharp.Tests/PuppeteerSharp.Tests.csproj --filter "FullyQualifiedName~TestName" --no-build -- NUnit.TestOutputXml=TestResults
-
-# Firefox should ALWAYS use bidi protocol
-BROWSER=FIREFOX PROTOCOL=bidi dotnet build PuppeteerSharp.Tests/PuppeteerSharp.Tests.csproj && BROWSER=FIREFOX PROTOCOL=cdp dotnet test PuppeteerSharp.Tests/PuppeteerSharp.Tests.csproj --filter "FullyQualifiedName~TestName" --no-build -- NUnit.TestOutputXml=TestResults
-```
-
-You can switch between CDP and Bidi by changing the PuppeteerTestAttribute.IsCdp property.
-You can switch between Chrome and Firefox by changing the PuppeteerTestAttribute.IsChrome property.
-If you are fixing one single test, then you must run the entire test suite to confirm that you didn't break other tests.
-
-## Utilities and Helpers
-
-### Helper Classes (`Helpers/`)
-- `AsyncFileHelper`: File I/O operations
-- `AsyncMessageQueue`: Message queue for async processing
-- `ConcurrentSet<T>`: Thread-safe set
-- `DeferredTaskQueue`: Deferred task execution
-- `EnumHelper`: Enum utilities
-- `MultiMap<K, V>`: Multi-value dictionary
-- `RemoteObjectHelper`: Remote object handling
-- `TaskHelper`: Task utility functions
-- `TaskQueue`: Sequential task execution
-- `StringExtensions`: String utilities
-- `TempDirectory`: Temporary file management
-- `ProtocolStreamReader`: Binary stream reading
-
-### JSON Helpers (`Helpers/Json/`)
-- Custom JSON converters
-- JSHandle serialization/deserialization
-- Protocol message serialization
-- Supports System.Text.Json
-
-## Key Design Patterns
-
-### 1. Abstract Factory Pattern
-- Protocol-specific implementations behind abstract base classes
-- Browser, Page, Frame, etc. have Cdp and Bidi variants
-- Factories create appropriate implementation based on protocol
-
-### 2. Template Method Pattern
-- Base Page/Frame classes define algorithm structure
-- Abstract methods for protocol-specific steps
-- Subclasses implement protocol details
-
-### 3. Task-Based Concurrency
-- Async/await throughout
-- TaskQueue for sequential operation ordering
-- TaskManager for tracking concurrent operations
-
-## Continuous improvement
-
-Every time you find a code style error during builds, for instance rules failures like "SA1648". Update this document to include the new rule and a brief description of how the codebase adheres to it. This will help maintain a high standard of code quality and consistency throughout the project.
diff --git a/lib/PuppeteerSharp.Tests/NetworkTests/CdpHttpRequestTests.cs b/lib/PuppeteerSharp.Tests/NetworkTests/CdpHttpRequestTests.cs
index 47bccbb5d..b420ae218 100644
--- a/lib/PuppeteerSharp.Tests/NetworkTests/CdpHttpRequestTests.cs
+++ b/lib/PuppeteerSharp.Tests/NetworkTests/CdpHttpRequestTests.cs
@@ -6,13 +6,14 @@
 using NUnit.Framework;
 using PuppeteerSharp.Cdp;
 using PuppeteerSharp.Cdp.Messaging;
+using PuppeteerSharp.Nunit;
 
 namespace PuppeteerSharp.Tests.NetworkTests;
 
 [TestFixture]
 public class CdpHttpRequestTests
 {
-    [Test]
+    [Test, PuppeteerTest("HTTPRequest.test.ts", "CdpHTTPRequest", "should reconstruct postData from postDataEntries")]
     public void ShouldReconstructPostDataFromPostDataEntries()
     {
         var client = Substitute.For<CDPSession>();
@@ -46,7 +47,7 @@ public void ShouldReconstructPostDataFromPostDataEntries()
         Assert.That(request.PostData, Is.EqualTo("part1part2"));
     }
 
-    [Test]
+    [Test, PuppeteerTest("HTTPRequest.test.ts", "CdpHTTPRequest", "should fallback to postData if postDataEntries is missing")]
     public void ShouldFallbackToPostDataIfPostDataEntriesIsMissing()
     {
         var client = Substitute.For<CDPSession>();