The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
I built the most stripped-down API tester I could.
One feature only for v1: test an API.
No extra tabs, no clutter, no 47 settings.
Just request → response → done.
Open source too.
Try it: https://hi-playground.vercel.app
Would you actually use something this minimal day-to-day?
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Built my portfolio like a product, not a resume ✨
I wanted one place that shows how I think and build, not only what I've built. So I designed and coded it from scratch😍
→ A case study for each project, covering the problem, the build and the outcome
→ Smooth Framer Motion interactions that don't slow anything down
→ Fully responsive, SEO-friendly and tuned for performance
→ Built with Next.js, TypeScript and Tailwind, and deployed on Vercel
Inside you'll find my AI publishing platform, a RAG app that lets you chat with any PDF, and more of my full-stack and GenAI work.
I'm open to freelance projects in Next.js, FastAPI and LLM-powered apps. If you have something in mind, send me a message.
Cream trailer is better because the cargo light creamy color has better contrast with an environment it and black truck feels dangerous🔥🔥🔥
Great job Vaskrsije🎉🎉🎉
A green test suite doesn't always mean your code is correct.
One thing I've been thinking about while building AI-powered developer tools is how easily a test can pass without actually verifying the behavior that matters.
For example, a test might call a method and finish with assertTrue(true). Everything looks green, but the test hasn't proved that the expected behavior works.
AI coding assistants make writing code and tests faster. That makes it even more important to ask a few questions before merging:
Does the test verify the behavior the PR changes?
Are mocks hiding the behavior we're supposed to test?
Would the test catch a broken implementation?
Are we reviewing the wider impact, not just the changed lines?
These questions have influenced how I'm building CodeGuard AI, a self-hosted GitHub PR reviewer that analyzes code changes alongside repository context and supports custom team rules.
I'm curious about other developers' experiences:
What's the most misleading passing test you've encountered in a real project?
I'd love to hear how you caught it.
