What If Your Users Ran Your E2e Tests?
Posted2 months agoActive2 months ago
faultsense.orgTechstory
calmpositive
Debate
0/100
E2e TestingCrowdsourced TestingQuality Assurance
Key topics
E2e Testing
Crowdsourced Testing
Quality Assurance
The story introduces Faultsense, a platform that allows users to run E2E tests, and the discussion revolves around its potential benefits and implementation challenges.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
25m
Peak period
2
0-1h
Avg / period
2
Key moments
- 01Story posted
Nov 2, 2025 at 7:35 AM EST
2 months ago
Step 01 - 02First comment
Nov 2, 2025 at 8:01 AM EST
25m after posting
Step 02 - 03Peak activity
2 comments in 0-1h
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 2, 2025 at 8:18 AM EST
2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45789864Type: storyLast synced: 11/17/2025, 7:49:00 AM
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.
Production for the frontend is the user’s device, and we all know things can go wrong without an explicit error. With the current state of frontend observability tools, how do you tell when something should have happened but didn’t?
Too bad we can’t just have our users run `it('opens checkout modal on click', …)`, right? What if we could..
Maybe the world doesn’t need more HTML attributes, but it’s my best attempt so far at improving frontend observability. I think the ends justify the means.