Day 7: My new project! Building KitchenSync, a Chrome extension that makes cooking easier: 🥣 Save clear recipes 🗓️ Plan meals 🛒 Auto-generate grocery lists 📱 Send recipes to yourself with QR codes Sign up → kitchensyncextension.com #mealplanner #recipes #cookingapp #cooking
Day 9: Big milestone for KitchenSync: Just submitted my demo to the Instacart team. Last step before getting production API access. Excited to bring seamless “Add to Instacart” grocery lists to life inside the KitchenSync extension 🥕 #chromeextension #recipes #recipeapp #cooking
Day: 8 Progress day 🚀 • Got accepted into the Instacart Developer Program • Applied for an Impact Marketplace acc • Got Instacart List API working in my dev environment Now waiting on reviews for Impact + production API access. Very productive day🥳 kitchensyncextension.com
Day 7: Kitchen Sync Chrome Extension Tech Stack: 🎨 Vanilla JS + Chrome APIs 🔐 Supabase Auth + PostgreSQL 📧 Vercel Functions + Resend Email 💳 Stripe payments 🔄 Custom Chrome Extension ↔️ Supabase sync #codinginpublic #chromeextension #claudecode #vercel
Day 7: I decided to take a break from my Monday.com plugin for automation. I still think its a great project and will get back to it later!
Day 6: Great progress, I fixed oauth issues, connected release readiness to my test runs, and set up bug linking from Monday.com board to my failed tests if they have a bug under their name. My dashboard looks like this so far: #qaautomation #cypress #qadashbaord
Day 5: I am hitting some 429 errors with Monday.com because I am sending too many redundant requests when I open a test run. Currently working on caching some of these values in order to avoid making multiple calls at once. #qaproject #qaautomation #mondaydotcom
Day 4: I pulled the bugs into the Dashboard using the groupID's and displayed the count of each group. I also added to the settings page which group bugs should be sent and which group is considered complete. Will be working on this feature tomorrow.
Day 3: I decided that the user should create custom settings to designate the definition of duplicate bugs, what group new bugs should be sent to, different automation sections based on file path. Settings will live in a config row in db. #qa #automation #monday #plugin #sdet
Day 3: Today I successfully was able to create a bug with an assigned user and an update with the test failure details. Next step will be to have smart linking so that customers will know if an open bug is tied to the failure already. #mondayplugin #testautomation #qaengineer
My project I’m focusing on is a Monday.com plugin that integrates Cypress & Playwright test automation from CI/CD pipelines (GitHub Actions, Azure DevOps). It adds a dashboard to track runs and automatically log + manage bugs directly in Monday #cypress #monday.com
United States Тренды
- 1. #KonamiWorldSeriesSweepstakes 1,552 posts
- 2. Mitch McConnell 24.3K posts
- 3. Term 192K posts
- 4. #2025MAMAVOTE 1.61M posts
- 5. Andrade 9,529 posts
- 6. Tyla 28.9K posts
- 7. Carter Hart 2,958 posts
- 8. No Kings 154K posts
- 9. Budapest 18.5K posts
- 10. Somalia 32.3K posts
- 11. #TrumpShutdownBadForUS 5,441 posts
- 12. Big L 11.3K posts
- 13. Yung Miami 3,049 posts
- 14. Chanel 29.6K posts
- 15. Deport Harry Sisson 34.1K posts
- 16. Anya 16K posts
- 17. Dodgers vs Mariners N/A
- 18. Nick Khan N/A
- 19. Caresha 2,009 posts
- 20. ErgoChair X 1,236 posts
Something went wrong.
Something went wrong.