Azertio: The revolution in API and DB test programming

Goodbye to 'Glue Code': The new era of testing

If you have ever maintained a complex test suite with Cucumber and RestAssured, you know the problem well: what should be a clear specification in .feature files ends up buried under endless layers of step definition classes, state management, and pom.xml configurations. The programming of test infrastructure becomes a project as costly as the software it intends to validate.

This is where Azertio comes in, an open source tool designed to break this cycle. Instead of forcing the developer to write Java code for every minor step, Azertio opts for a purely declarative approach using YAML files and versioned plugins.

How does Azertio work?

The premise of Azertio is radically simple: the most common steps already exist. By installing specific plugins—such as rest or db—the user can run tests without writing a single line of additional source code.

Configuration over code

Instead of managing complex dependencies, everything is centralized in an azertio.yaml file. This eliminates classpath contamination and allows each plugin to run in its own module, avoiding version conflicts between libraries. Just as when we analyze the differences between modern development frameworks—as detailed in SvelteKit vs Astro 4: The ultimate duel in programming and performance—the choice of a testing tool should prioritize maintainability and clarity.

"Azertio allows for the separation of business intent from technical implementation through a two-level model, facilitating regulatory traceability and collaboration between teams."

Key features that make a difference

1. Definition vs. implementation model: It allows for business-readable @definition files and technical @implementation files that execute the logic, maintaining perfect traceability.
2. Integrated benchmark: You don't need external tools to measure performance. You can run functional and load tests using the same syntax, utilizing virtual threads for high concurrency.
3. Native persistence: Unlike other tools that rely on ephemeral XML reports, Azertio allows you to store execution history in a PostgreSQL database, queryable directly from a VS Code extension.

Comparison with other solutions

Although tools like Karate use javascript to add logic to their tests, this often turns test files into small programs that are difficult for non-technical profiles to read. Azertio, on the other hand, maintains a strict separation: feature files are declarative, and the logic resides exclusively in typed step providers written in Java.

Conclusion

Azertio is currently in the alpha phase, but its value proposition is clear: reduce the cognitive load of QA and transform testing from an engineering burden into living, executable documentation. If you are looking for a solution that avoids excessive coupling and prioritizes readability, it is time to keep an eye on this project in its official repository.

---

Sources: Dev.to (https://dev.to/luiinge/azertio-api-and-database-testing-without-the-glue-code-1ibl)