HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
lucgagan
auto-playwright
TypeScript2023–2024
lucgagan / auto-playwright

auto-playwright

Automating Playwright steps using ChatGPT.

2Distinct people
5Mentions
0Explicit recommenders
847GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Automating Playwright steps using ChatGPT.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week5 dated mentions

Observed mentions: 2023-11-11 14:41:34 UTC to 2024-05-07 21:04:26 UTC. Weeks start Monday, UTC.

0122023-11-06 00:00:00 UTC to 2023-11-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 62023-11-13 00:00:00 UTC to 2023-11-20 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023-11-20 00:00:00 UTC to 2023-11-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-27 00:00:00 UTC to 2023-12-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-04 00:00:00 UTC to 2023-12-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-11 00:00:00 UTC to 2023-12-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-18 00:00:00 UTC to 2023-12-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-25 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2024-01-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-08 00:00:00 UTC to 2024-01-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-15 00:00:00 UTC to 2024-01-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-22 00:00:00 UTC to 2024-01-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-29 00:00:00 UTC to 2024-02-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-02-05 00:00:00 UTC to 2024-02-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 52024-02-12 00:00:00 UTC to 2024-02-19 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-02-19 00:00:00 UTC to 2024-02-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-02-26 00:00:00 UTC to 2024-03-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-03-04 00:00:00 UTC to 2024-03-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-03-11 00:00:00 UTC to 2024-03-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-03-18 00:00:00 UTC to 2024-03-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-03-25 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-01 00:00:00 UTC to 2024-04-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-08 00:00:00 UTC to 2024-04-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-15 00:00:00 UTC to 2024-04-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-22 00:00:00 UTC to 2024-04-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-29 00:00:00 UTC to 2024-05-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-05-06 00:00:00 UTC to 2024-05-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 6

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Nov 62023-11-06 00:00:00 UTC2023-11-13 00:00:00 UTC101
Nov 132023-11-13 00:00:00 UTC2023-11-20 00:00:00 UTC211
Nov 202023-11-20 00:00:00 UTC2023-11-27 00:00:00 UTC000
Nov 272023-11-27 00:00:00 UTC2023-12-04 00:00:00 UTC000
Dec 42023-12-04 00:00:00 UTC2023-12-11 00:00:00 UTC000
Dec 112023-12-11 00:00:00 UTC2023-12-18 00:00:00 UTC000
Dec 182023-12-18 00:00:00 UTC2023-12-25 00:00:00 UTC000
Dec 252023-12-25 00:00:00 UTC2024-01-01 00:00:00 UTC000
Jan 12024-01-01 00:00:00 UTC2024-01-08 00:00:00 UTC000
Jan 82024-01-08 00:00:00 UTC2024-01-15 00:00:00 UTC000
Jan 152024-01-15 00:00:00 UTC2024-01-22 00:00:00 UTC000
Jan 222024-01-22 00:00:00 UTC2024-01-29 00:00:00 UTC000
Jan 292024-01-29 00:00:00 UTC2024-02-05 00:00:00 UTC000
Feb 52024-02-05 00:00:00 UTC2024-02-12 00:00:00 UTC000
Feb 122024-02-12 00:00:00 UTC2024-02-19 00:00:00 UTC110
Feb 192024-02-19 00:00:00 UTC2024-02-26 00:00:00 UTC000
Feb 262024-02-26 00:00:00 UTC2024-03-04 00:00:00 UTC000
Mar 42024-03-04 00:00:00 UTC2024-03-11 00:00:00 UTC000
Mar 112024-03-11 00:00:00 UTC2024-03-18 00:00:00 UTC000
Mar 182024-03-18 00:00:00 UTC2024-03-25 00:00:00 UTC000
Mar 252024-03-25 00:00:00 UTC2024-04-01 00:00:00 UTC000
Apr 12024-04-01 00:00:00 UTC2024-04-08 00:00:00 UTC000
Apr 82024-04-08 00:00:00 UTC2024-04-15 00:00:00 UTC000
Apr 152024-04-15 00:00:00 UTC2024-04-22 00:00:00 UTC000
Apr 222024-04-22 00:00:00 UTC2024-04-29 00:00:00 UTC000
Apr 292024-04-29 00:00:00 UTC2024-05-06 00:00:00 UTC000
May 62024-05-06 00:00:00 UTC2024-05-13 00:00:00 UTC101

What Hacker News says

5 sources
lucgagan·Nov 15, 2023Submission

Ask HN: What constitutes plagiarism in open-source?

I recently have been called out for plagiarism in a Reddit thread. https://www.reddit.com/r/programming/comments/17tccsc/comment/k8w5o26/?utm_source=… I shrugged it off the first time it popped up, because in my eyes the person making the comment is more sour that I am impeding their ability to monetize the concept by making it open-source than they actually believe that I cloned their work. However, the same user then started spamming my project users with their messages about this project being a clone of theirs without proper attribution and going as far as to double down by posting a new thread on /r/programming once again stating that it is a clone. https://www.reddit.com/r/programming/comments/17w3toy/comment/k9etf1x/?utm_source=… I saw this thread a few hours late, so b
Read the rest
y the time I got to respond everyone already had their pitchforks out. Bursting out a few responses in panic probably didn't help either. Anyway, that's the context. The projects in question are https://github.com/zerostep-ai/zerostep and https://github.com/lucgagan/auto-playwright. I added a section to the documentation using every concrete piece of evidence I could think of to prove that these projects are as distinct as they possibly can be given the narrow scope of the problem and possible ways to implement it (https://github.com/lucgagan/auto-playwright#addressing-controversy). I also think that, in retrospect, it would have been nice of me to acknowledge that their project was a source of inspiration for Auto Playwright. However, at no point did I copy their project, so the thought of LICENSE attribution did not even cross my mind. I am trying to be cool head about this and think of what is the proper response. More importantly, I am trying to get a perspective from folks outside of the original debate to see if I am wrong with my actions. Is copying parts of README enough to call for attribution to the original project? Is copying error message enough to call for attribution of the original project? Where is the line? I still think this whole think exploded because I effectively released something that provides comparable functionality to a commercial solution that they are working and thats what spurred this debacle. However, I also acknowledge that I am struggling to reconcile dozens of people calling me "** code thief" in private messages and my sense of righteousness, which is why I would appreciate the insights.
1 points · Open discussion
Hello HN community! I'm excited to introduce Auto Playwright, an open-source tool that revolutionizes web testing by integrating AI with Playwright. Imagine writing your web app tests in plain, simple English and having AI turn those instructions into automated tests! Key Features: - AI-Driven Test Writing: Just write what you need in plain text, and let the AI do the rest. - Playwright Compatibility: Works with all browsers compatible with Playwright. - Open-Source: Dive into the code, contribute, and customize as you see fit. How It Works: 1. Install `auto-playwright` via npm. 2. Set up your OpenAI API key. 3. Write tests using intuitive, plain-text prompts. Examples: From testing a search function with a few lines of text to automating complex e-commerce cart tests – it's all made incredibly simple. test("auto Playwright example",
Read the rest
async ({ page }) => { await page.goto("/"); // `auto` can query data // In this case, the result is plain-text contents of the header const headerText = await auto("get the header text", { page, test }); // `auto` can perform actions // In this case, auto will find and fill in the search text input await auto(`Type "${headerText}" in the search box`, { page, test }); // `auto` can assert the state of the website // In this case, the result is a boolean outcome const searchInputHasHeaderText = await auto(`Is the contents of the search box equal to "${headerText}"?` { page, test }); expect(searchInputHasHeaderText).toBe(true); }); Why It Matters: This isn't just about automating the usual; it's about rethinking test automation. It's faster, more intuitive, and accessible, even for those less familiar with traditional coding. Get Involved: I am building a community around Auto Playwright. Join us on Discord (https://ray.run/discord), contribute to the GitHub repo (https://github.com/lucgagan/auto-playwright), and stay updated with our newsletter (https://ray.run/newsletter). Looking forward to your thoughts, feedback, and seeing how you use Auto Playwright in your projects! Check out Auto Playwright on GitHub: https://github.com/lucgagan/auto-playwright
In [dead]

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.