liudasjank

4 ms·

1.
Automation Before Automation (ABA)(zenodo.org)
3 points by liudasjank 4mo ago|0 comments
2.
by liudasjank 9mo ago
It’s truly alarming to see the numbers laid out like this. Over 7,000 mass shootings in the U.S. since 2013, that's an average of about 1.5 mass shootings every single day. This means someone is opening fire on four or more people roug
3.
Rentgen is not a Postman replacement, it fills gap Postman never tried to fill(rentgen.io)
1 points by liudasjank 10mo ago|0 comments
4.
What a Real Jira API Request Reveals Under Rentgen Testing(rentgen.io)
2 points by liudasjank 10mo ago|0 comments
5.
by liudasjank 10mo ago
There were two major problems: one serious enough to be a Bug Bounty submission, the other simply a clear backend bug: 1.CORS policy was wide open Anyone could call the internal ChatGPT API endpoint from any domain. Regardless of authentica
6.
by liudasjank 10mo ago
A bit more technical context on how I tested this, since people usually ask about methodology. I took the exact cURL from the browser’s network tab and generated variations around it: missing fields, oversized body, invalid types, wrong met
7.
ChatGPT's back end: crashes, echoing payloads, and fast fixes(github.com)
2 points by liudasjank 10mo ago|1 comments
8.
by liudasjank 10mo ago
Thanks for the thoughtful suggestions, those are spot on. Rate-limit testing and proper 429/Retry-After handling are definitely on the roadmap. Idempotency checks for POST/PUT are a great call too, a lot of APIs behave unpredictab
9.
I built an API testing tool that generates tests from a single cURL(github.com)
4 points by liudasjank 10mo ago|4 comments
10.
by liudasjank 10mo ago
The idea came from a simple problem: most teams have lots of API endpoints, but almost no one has realistic coverage. Writing and maintaining test collections takes forever, and scripts always fall out of sync. Rentgen takes one cURL reques