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

How to get a green Playwright TypeScript suite in under 5 minutes with Agentic Playwright

Scaffold a running Playwright and TypeScript test project and see the smoke test pass before writing any code.

Who it is forA QA engineer or developer starting a new end-to-end test project who wants a working baseline before adapting it to their own app.

The problemSetting up a Playwright TypeScript project with page objects, fixtures, configuration, and a browser install takes time before any test can run.

The outcomeA scaffolded project with dependencies and a browser installed, and a passing smoke test run against the bundled demo application.

What you need first

  • Node.js v22.x or later
  • npm v10.x or later
  • An empty directory or empty git repo for the test project
  • A web application URL to test, or the --demo option to try the bundled demo app

Steps

  1. Create an empty directory for the tests, or clone an empty git repo, and open a terminal in it.
  2. Run npm create agentic-playwright . -- --demo.
  3. Wait for the scaffold to install dependencies and a browser, then for the smoke test to run against the demo application.
  4. Confirm the smoke test is green, then open the example files such as the page objects and login spec to see the patterns.
  5. Replace the example pages and tests with your own application's pages and tests.

Prompt for your agent

In the agentic-playwright repo, run `npm create agentic-playwright <target-folder> -- --demo` from an empty <target-folder>. Expected output: the scaffold installs dependencies and a browser and the smoke test passes against the demo app. Verify the smoke test result is green before making any changes.

Caveat. The bundled files are examples only, so the README says they must be replaced with your real application's pages, tests, and data.

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