You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: lib/.claude/commands/implement-bidi-feature.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,8 +11,8 @@ In order to do that you will need to:
11
11
* You are going to look for tests that might match that `testIdPattern` but looking at the test attribute.
12
12
- For instance if the `testIdPattern` is `Chromium-Specific *`, `[Test, PuppeteerTest("chromiumonly.spec", "Chromium-Specific Page Tests", "Page.setRequestInterception should work with intervention headers")]` will be a valid match.
13
13
* Once you see what fail in those tests you will need to modify the code to make the test pass. You should not edit the tests themselves.
14
-
* You will find the code in typescript implementing the feature at ../../puppeteer/puppeteer and you will need to port that code to .NET.
15
-
* You will also find BidiDriver code at ../../puppeteer/bidi-client you need to check what you need to use from there to make the tests pass.
14
+
* You will find the code in typescript implementing the feature at ../../../puppeteer/puppeteer and you will need to port that code to .NET.
15
+
* You will also find BidiDriver code at ../../../webdriverbidi-net/webdriverbidi-net you need to check what you need to use from there to make the tests pass.
16
16
* You will have to implement the code as close as possible to the original code, but adapted to .NET idioms and practices.
17
17
* 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.
18
18
* You need to run related tests to ensure everything is working as expected.
0 commit comments