QA-Use-Mcp: Mcp for E2e Testing
Posted3 months agoActive3 months ago
npmjs.comTechstory
supportivepositive
Debate
20/100
TestingQuality AssuranceNpm Packages
Key topics
Testing
Quality Assurance
Npm Packages
The post introduces 'qa-use-MCP', an npm package for end-to-end testing, and the discussion revolves around its utility and potential applications in testing workflows.
Snapshot generated from the HN discussion
Discussion Activity
Moderate engagementFirst comment
N/A
Peak period
6
96-108h
Avg / period
2.3
Key moments
- 01Story posted
Oct 6, 2025 at 5:00 AM EDT
3 months ago
Step 01 - 02First comment
Oct 6, 2025 at 5:00 AM EDT
0s after posting
Step 02 - 03Peak activity
6 comments in 96-108h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 11, 2025 at 6:20 AM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45489274Type: storyLast synced: 11/20/2025, 2:49:46 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Funny enough, one of the most challenging things while building it was to be able to remotely control the browser that runs locally (been using https://localtunnel.me/ for it), while making sure that it does not impact the user too much.
Also, I wondered if there's someone that is shipping CLIs with an "mcp" command, as seems that having a normal CLI for the funcionatilitie sof the MCP would make a lot of sense + with the option of running it as an MCP if the user wants to.
Have you seen this pattern?
Also, as there's a lot of buzzwording around MCPs, any of you that been using an MCP as a daily driver? For me it was the github one, specially for code search and stuff like that.
Also about the CLI thing you mention, we had cases where people did not use MCP clients, so I actually wanted to expose a way to interact with the tools directly without the need of the server running!
This is cool! no shade at all to desplega.ai but I would love a version of this that runs locally + does stuff like verifying no tests are flaky. I do this with a few extra steps via claude code + playwright tests. e2e tests are the best way I know for catching UI regressions but they're expensive and annoying to run, so something that looked at a PR and healed / wrote tests in the background as I work on features would be pretty cool.
Why local? Basically I'm just cost sensitive for my own projects and already have this nasty MacBook that only gets like 20% utilization.
If your challenge is flakiness, this should help initially. Unfortunately, there’s a lot of work in our engine, and a custom system to handle operations that goes beyond vanilla Playwright so running it locally would be quite challenging.
Also part of our format is specially finding deterministic way of running steps, with automatic healing when failed. And we also build the whole system in a way that is self-hostable, so in the cases you mention you could be able to have control over what is run and where.