Liudas Jankauskas

Hey everyone! We ve released Rentgen v2.0.0

Rentgen tests your API from a single cURL: map your fields, click run, and get validation, boundary, security, authentication, and performance checks. Core testing runs locally and is free.

For years I've seen teams perform the same activity: A feature is implemented. Before anyone creates a maintainable automation suite, developers and testers spend time exploring the system. Sometimes manually. Sometimes using fuzzers, mutation tools, schema generators, protocol analyzers, API scanners, AI-assisted tools, or other forms of generated testing. The goal is not regression protection. The goal is discovery.

Hundreds of tests may be generated and executed. Many are never maintained. Some reveal defects. A few become future regression tests. Yet we usually classify this activity as either exploratory testing or test automation, even though it doesn't fully fit either category.

I saw this meme and honestly it s so far from reality.
We keep talking about shift-left, testing earlier, bringing QA into development and then we share memes like this, implying API testing somehow doesn t make sense. First of all, API itself can be the product. Second: even if it s not - API always needs to be tested separately. Different bugs. Different rules. Different risks. You don t test API like a user clicks a UI.
You test: success paths, validation errors, auth mechanisms, rate limiting, performance, edge cases and many others.
Most of which you can t even properly test through the UI. That s the whole point.
And this is exactly why we built Rentgen.io
To take care of these boring, but critical checks instantly - without setup, without writing tests, without pretending clicking buttons will somehow cover your backend.
Automation before automation.