The problem
In many projects, authentication APIs (such as login or token generation) are used everywhere.
Without a central API definition, teams often redefine the same login request inside every test case.
This leads to duplicated logic, inconsistent parameters, and high maintenance cost when the login response or contract changes.
A small change in the login API can silently break dozens of test cases, forcing testers to update each one manually.
How AXQA solves it
AXQA’s API Manager introduces a single source of truth for authentication APIs.
The Login API is defined once, with its parameters, authentication rules, and response structure.
Test cases don’t redefine the API — they simply reference it.
When the login response changes, the API is updated in one place, and all dependent test cases automatically use the new behavior.
How to implement it using API Manager
- Create a new API Definition named “Login API”
- Set the endpoint, method, and authentication type
- Define parameters such as username and password
- Add example request and expected response schema
- Reference this API inside multiple test cases instead of redefining it
Result: consistent authentication logic across the entire project with zero duplication.