DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run regression tests before changing the extension with Browser Kitten

Run the Node and browser smoke tests to confirm a baseline before editing Paw Work.

Who it is forA developer who wants to modify the extension and needs a known-good baseline first.

The problemEdits to an agent extension can break runtime behavior that is hard to spot by reading code.

The outcomeA pass or fail result for the pure Node regression suite and the browser smoke test on the unmodified code.

What you need first

  • Chrome 135 or newer
  • An OpenAI-compatible API key to paste into the side panel (BYOK)
  • Developer mode enabled on chrome://extensions
  • A clone of the repo or a Release zip download

Steps

  1. Clone the repo and open a terminal in its root folder.
  2. Run node --test tests/runtime-regression.test.mjs to execute the pure Node regression tests.
  3. Run node tests/browser-smoke.cjs to load the real extension and run the smoke test.
  4. If the browser smoke test fails with CDP_BUSY, close DevTools on the target tab and run it again.
  5. Record the results before you make your change.

Prompt for your agent

In the PawWork repo at <repo path>, run `node --test tests/runtime-regression.test.mjs` and then `node tests/browser-smoke.cjs`. Report the pass or fail count for each and list any failing test name. Verify that the Node suite runs without a browser.

Caveat. The browser smoke test loads the real extension, so it needs Chrome installed and a clean target tab, and the README gives no further setup detail.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page