{
  "video_id": "reddit_1uhu8s4",
  "channel_slug": "ClaudeAI",
  "channel_handle": "r/ClaudeAI",
  "title": "$20 of lapdance in Miami last longer than $20 of tokens with Claude",
  "url": "https://www.reddit.com/r/ClaudeAI/comments/1uhu8s4/20_of_lapdance_in_miami_last_longer_than_20_of/",
  "external_url": null,
  "upload_date": "20260628",
  "published_at": "2026-06-28T10:54:05+00:00",
  "transcript": "I was lazy enough to click around UI and test a new feature. That would take me 10 minutes, so asked Claude. \n\nI've adopted a workflow where I do not care about how UI is built at all, pure vibe-code, as long as the backend is secure and sound.\n\nClaude Code is quite good at manual e2e testing, especially while it works on the feature. But also it's quite expensive to have claude come up with the plan and run it every single time, especially when feature is evolving. Like button may not work, wrong paddings, looks bad on mobile, etc.\n\nHow are you guys automating it?\n\n\n\n--- Top Comments ---\n\n\n[34 upvotes] You should work on your model selection, prompt quality, and stamina so you don’t bust during those dances.\n\nBut really if you’re fine with figuring out the UI/UX by brute force iteration, it’s going to get expensive. Claude is like that other guy’s wife, she wants to be told exactly what to do.\n\n[10 upvotes] Bruh 😂😂😂\n\n[10 upvotes] I use playwright MCP to test the UI. Instead of asking it to test once, you can ask it to create an automation framework and create test scripts. If you want to rerun, you can ask it to run, monitor and fix any bugs it comes across. \n\nThis way claude won't waste tokens doing the same thing over and over again. \n\n[8 upvotes] crazy title ",
  "transcript_chars": 1283,
  "ingested_at": "2026-06-28T13:30:03.892117+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 100,
    "upvote_ratio": 0.82,
    "num_comments": 31,
    "author": "Slow_Watercress_4115",
    "is_self": true
  }
}