Liudas Jankauskas

Liudas Jankauskas

Rentgen.io nex-gen API testing tool
#92490911 follower23 following
2 points
đź‘Ź 11 day streak
All activity
Liudas Jankauskasleft a comment
Most teams test features. Almost nobody tests HTTP behavior. That’s why these bugs keep shipping. I’ve been collecting these checks into a small local tool: https://github.com/LiudasJan/Rentgen No AI. No cloud. No accounts. No telemetry.
Liudas Jankauskas
After testing hundreds of APIs, the biggest issues are still HTTP basics
Liudas JankauskasJoin the discussion
Liudas Jankauskasstarted a discussion

After testing hundreds of APIs, the biggest issues are still HTTP basics

After years of testing APIs across fintech, gov, and internal platforms, I keep seeing the same pattern: Most API bugs are not complex. They’re boring HTTP basics that teams quietly forget. A few examples I see again and again: Missing auth returns 403 instead of 401 — so clients debug permissions instead of authentication Unsupported HTTP methods return 200 — so people debug payloads instead...

Liudas Jankauskasleft a comment
Github copilot - removes boilerplate and speeds up implementation, without pretending to understand the system better than I do.
Aaron O'Leary
🔥 Best AI Automation Tools: Nominate Your Favorites for the Product Hunt Orbit Awards
Aaron O'LearyJoin the discussion
Liudas Jankauskasleft a comment
This solves very specific but very real bottleneck. Curious how you ensure testers actualy use the app, not just install and idle to meet the 12-tester rule?
BetaCircle
BetaCircleGet 12 android testers for 14 days in Closed Testing
Liudas Jankauskasleft a comment
Interesting approach. One thing I’m curious about how do you make failures visibe? When a scout prunes a path - do I see what faild? And why? And whas cause it? Because without explicit failure signals system like this can look impressive, but hard to trust.
Dropstone
DropstoneThe Recursive Swarm IDE. 10,000 Agents in one tab
Liudas Jankauskasleft a comment
From my experience leading API testing teams, the biggest problems aren’t a lack of tools — it’s the gaps in what people actually test. Some recurring issues: Boundary values are almost never tested (min/max, overflow, negative ranges). ENUM or “allowed values” checks are skipped because they’re boring to maintain. Developers rely on happy-path requests and miss trimming/whitespace/invalid-type...
Nikolas Dimitroulakis
Testing APIs. Biggest Problems?
Nikolas DimitroulakisJoin the discussion
Liudas Jankauskasstarted a discussion

I spent 18 years breaking software, now I built a tool that does it faster than I ever could

I’m Liudas — a QA engineer with 18 years of experience in backend/API testing, leading QA teams in security-critical environments in the UAE. I built Rentgen because most API bugs are simple edge cases no one has time to test manually. One cURL → hundreds of generated test cases. All local, no cloud, no telemetry. I believe in no-nonsense engineering, fast feedback loops, and tools that help...